On 23.07.2015, at 17:01, Marshall Schor <[email protected]> wrote: >> The way we use UIMA is that we let it process our content with different >> custom pipelines, and at the end of each pipeline the results are converted >> into POJOs and those are written into a database, all code which follows >> just uses the POJOs to process the data. My point is: If the CAS would be >> in a better state we could just use it through out the entire application >> instead of our CAS-like layer. > > In version 3, we're planning on storing the Feature Structures as just > instances > of their JCas Java Cover Objects, pretty close to POJOs. So maybe there's a > good > chance...
You mean as "instances of Java Cover Objects" without "JCas", right? I mean there should still be the possibility to work with the CAS without JCas objects, basically via the CAS interface, no? We shouldn't have to use some Java reflection and bean utils to work with JCas - and there was also one wish for a more schemaless CAS which contradicts only having a strongly typed JCas API. Cheers, -- Richard
