Hey, Thanks for the response.
I actually have been using uimaFIT. And while it provides a lot of convenience, it only uses spring as detailed here: http://code.google.com/p/uimafit/issues/detail?id=40 The library allows you to use @ExternalResource annotations to have dependencies "injected", but each dependency requires a separate ExternalResourceLocator (the uimaFIT convenience wrapper for UIMA's Resource) implementation, and still doesn't solve the dependency resolution issue between dependencies. I suppose I was hoping for some kind of magic in UIMA AS. On Sat, Mar 19, 2011 at 2:54 PM, Tommaso Teofili <[email protected]>wrote: > Hi Alex, > I think you could take inspiration from the (Spring based) DI support in > uimaFIT [1], even if, personally, I'd recommend the use of Guice instead of > Spring. > My 2 cents, > Tommaso > > [1] : http://code.google.com/p/uimafit/ > > 2011/3/18 Alex Chaphiv <[email protected]> > >> Hi, >> >> I have several annotators that require objects that are rather complex to >> build. >> I've been able to get around this using by using ExternalResources with >> custom >> api interfaces, but it requires a lot of boilerplate and doesn't allow for >> sharing of dependencies between ExternalResources. >> >> So what would be the best way to get around this? Even better, is there >> any >> support for Spring or Guice? >> >> >
