Eddie Epstein wrote: > On 5/14/07, Adam Lally <[EMAIL PROTECTED]> wrote: >> 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. > > There's no question that these methods should work for single view > annotators; that is a given. To have it work for some multi-view > annotators but not others does not seem like an advantage. A warning > should be given that these methods should not be used for a multi-view > annotator. > > Another thing to consider is non-JCas cover classes. Ideally all cover > classes would point at the base CAS, as all FS exist in the same heap, > shared for all views. Would be nice for both CAS and JCas cover > classes to have the same simple model. > > Eddie
Sorry, stupid question from a non-Sofa aware developer. I lost the thread of this discussion right at the start. Why does the JCas need to know about views? Why can't it just use the view information that's in the CAS? When I get to an annotation by dereferencing, that annotation already lives in some given view, known to the CAS. That's the one that needs to be used, right? I'm probably missing the point entirely here, so please enlighten me. --Thilo
