>> This is quite "custom" and I don't like it very much to pass ClassLoaders >> between bundles however it could be good to implement a >> OSGiUIMAFrameworkImpl class which hides such details to the developer who >> wants to run UIMA inside OSGi environments. > > As far as my understanding goes, we can either add some "fixes" to > make UIMA as it is now work in an OSGi environment or we can > redesign a few things to migrate to OSGi. > The later option might only be possible with breaking backward > compatibility.
I don't think UIMA should mandate the use of OSGi. It would be nice though, if the UIMAFramework class would be opened up for customization. While UIMA is implemented in a highly modular fashion, the current implementation of the UIMAFramework defies any attempt of actually customizing it, e.g. providing custom factories. For the uimafit-spring experiment, I had to do some ugly reflection hacks to replace the default component factories with instances that run UIMA component instances through the dependency injection. I could imagine that OSGi support could also come as a custom option that can be added to the core UIMA framework if desired. -- 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 -------------------------------------------------------------------
