1 Oct 2011 04:33
Re: CAS Id
> How does UIMA-AS currently do the linking of the network-ID to the CAS? Do you use the CAS instance as the key in a hashmap or something like that? When the CollectionReader fills a CAS the UIMA-AS client assigns it an ID generated by java.rmi.server.URI.URI() before sending it to the service queue. So even if there is only one CAS in the pool it gets a new ID each time it is reused. I'd like to see this ID become part of the CAS object, set by core UIMA whenever a new CAS is filled by a CR or CM. The other use case for what I think of as a document ID would be the same even if different pipelines process the CAS at different times. I assume it would be set by the CR or CM, not by the framework. Since events can be documented with audio & video as well as with text, I think it's OK to use "document" to refer to the Sofa data in a CAS. By convention we've assumed additional views are alternative representations of the same artifact (although they could be entirely independent) so the document ID could apply to the whole CAS. ~Burn
)
This would be a 2.4.0 release (due to some slight change in the JMX APIs that
Jerry did, and the rather extensive evolving of the Cas Editor).
I'd like to precede this with a "build" tooling update. For that, it would be
nice if we could get the "m2e" maven/eclipse for Eclipse 3.7 working - I tried
this twice, and as of last month it was almost getting to the point where I
could make it more-or-less work, but not quite.
Has anyone gotten this to work yet? If so, can you post what you needed to add
to our POMs to get it to go? (that is - m2e reads configuration out of
org.eclipse.m2e:lifecycle-mapping that you can use to make things build in
Eclipse the same way (more-or-less) that they build in maven.
I'm thinking m2e needs a little more time before it starts working reliably, so
happy to defer this...
-Marshall
RSS Feed