On 5/14/07, Eddie Epstein <[EMAIL PROTECTED]> wrote:
JCas objects are broken if an FS instance can belong to multiple
views, because 1) addToIndexes() is ambiguous and 2) hashed JCas
instances are not shared across views. The suggestions above do not
fix the situation for all scenarios, for example, situations where a
JCas object is retrieved from a reference.
Given that there is no complicated approach that always works, a
simpler approach is called for: just have one set of xxx_Type objects,
deprecate addToIndexes() and always map it to the current view.
I prefer that we deprecate addToIndexes() and removeFromIndexes() but
take reasonable steps to make the methods behave is closely to the
current behavior as possible. If Marshall is willing to implement
something a little more complex that reduces the chance of breaking
annotators, then I think that would be good.
The issues with obtaining a JCas object by a reference are not ideal,
but we're digging pretty deep to turn up these situations. Ideally
I'd like it if everything worked as before, but if we can't manage
that I think we're close enough.
-Adam
