Thilo Goetz wrote:
Changes look ok, but I'm wondering: we now have CAS, CommonCas,
AbstractCas and AbstractCas_ImplBase, all in org.apache.uima.cas. Why
is AbstractCas_ImplBase in the interfaces package? Can we please move
it to the appropriate impl package? Any chance we can consolidate
Ab
Thilo Goetz wrote:
Marshall Schor wrote:
Thilo Goetz wrote:
From a performance perspective, I'd vote for having the filtering on
the iterator side of thing, where it already is. If one annotator
decides it needs a "filtered index" over annotations, that can
affect the performance of all ot
Some clarifications below:
Thilo Goetz wrote:
Marshall Schor wrote:
Using the definitions Adam defined:
* "CAS" means the entire CAS. It never means a specific view of the
CAS.
* "Index Definition" means the declaration in the descriptor that
defines an index - giving it a label, kind of in
Marshall Schor wrote:
Thilo Goetz wrote:
From a performance perspective, I'd vote for having the filtering on
the iterator side of thing, where it already is. If one annotator
decides it needs a "filtered index" over annotations, that can affect
the performance of all other annotators as we
Adam Lally wrote:
On 12/22/06, Marshall Schor <[EMAIL PROTECTED]> wrote:
> Also, we have some uses of non-annotation indexes that are segregated
> by Sofa (say, a Lemma index that's particular to a Sofa, where there's
> actually no explicit link from the Lemma to the Sofa). A filtering
> appr
Marshall Schor wrote:
Using the definitions Adam defined:
* "CAS" means the entire CAS. It never means a specific view of the CAS.
* "Index Definition" means the declaration in the descriptor that
defines an index - giving it a label, kind of index, CAS type, and
sort keys.
* "Index" is an inst
Jörn Kottmann wrote:
Hi,
it would be nice to have a facility to listen to changes made to a CAS
object.
In a SWT/RCP application its likely that multiple views display
concurrently some aspects of the CAS object,
if now one view makes a change to the CAS object all other views must be
sync
Changes look ok, but I'm wondering: we now have CAS, CommonCas,
AbstractCas and AbstractCas_ImplBase, all in org.apache.uima.cas. Why
is AbstractCas_ImplBase in the interfaces package? Can we please move
it to the appropriate impl package? Any chance we can consolidate
AbstractCas and Common