hi david, AFAIK there should be no problem with getting components from a ServiceManager. behind the scenes an ExcaliburComponentManager is wrapped by a WrapperServicerManager which delegates to the ECM and creates those proxies you mentioned. one point regarding ServiceSelector's: since proxies are being used you have to make sure that you have the respective service interfaces defined. otherwise you'll get ClassNotFoundException's. apart from that you shouldn't have any problems.
> -----Ursprungliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Auftrag > von David Kavanagh > Gesendet: Donnerstag, 31. Juli 2003 22:18 > An: [EMAIL PROTECTED] > Betreff: service manager Q > > > I'm getting my GenericTaskManager stuff running under 2.1rc1 and ran > across a snag. I thought 2.1 was switching over to the whole Serviceable > interface. So, I make this action I wrote implement Serviceable and ask > the ServiceManager for a component that is defined in the cocoon.xconf > file (the GenericTaskManager) and I get some class back called > "$Proxy2"! So, that is an inner class with no package! > I look around the code and it looks like the ExcaliburComponentManger is > still being used which deals just with Components. Should I even try > asking the ServiceManager for components defined in the cocoon.xconf file? > > David >
