Not sure if this will help, but the CAS supports a concept of multiple "views", where each view is itself a CAS object. The process(cas) method can then be passed a specified view, so that the annotator only deals with a subset of the entire CAS. Some have used views to deal with complex documents, creating a view for each of several document parts and then passing specified view(s) to the appropriate AE.
For more on CAS views, see http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tutorials_and_users_guides/tutorials_and_users_guides.html#ugr.tug.mvs Regards, Eddie On Tue, Nov 25, 2008 at 4:11 PM, Thomas Polzin <[EMAIL PROTECTED]> wrote: > I probably missed something in the documentation but here is my problem: > > > I'm trying to process a pretty complex structured document and I do not > want to translate the entire structure into annotations. Instead I would > like to pass some object containing this additional structure to the > respective analysis engines. Note that a static object will not work. > Also, I do not want pass this object to the engines when they are > constructed/initialized. The best solution I came up with so far is to > subclass the CAS object and then to downcast to it in the process( CAS > cas) function. Does this make sense? Is there a better solution? > > Thanks so much in advance > > Thomas > >
