> For example: > A user wants to build an AAE out of three different AEs, made by three > different > vendors. Then he might run into issues with the type system, especially when > one > used JCas, he needs eventually to duplicate certain pieces of configuration, > etc. > > I believe these things should be easier, and then it is also easier to > properly support OSGi.
I don't see how type system issues are related to class loading and component discovery issues. The first are related to the lack of standards on the level of annotations/metadata, the latter are related to the component framework architecture. Being spoiled by uimaFIT, I don't have much of a problem moving duplicate stuff into a factory function or variable and injecting it where I need it. But there is currently no way to plug in class loaders, change factories or discover component implementations. uimaFIT at least provides a way to discover type systems (very convenient!). Discovering components would be nice too though -- preferably without having to deal with UIMA XML descriptors. Cheers, Richard -- ------------------------------------------------------------------- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 eckar...@tk.informatik.tu-darmstadt.de www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de -------------------------------------------------------------------
