Hi, If you want your components to be functional in both Cocoon and Merlin, you need to follow;
1. Make a ROLE = MyService.class.getClass() in the service interface. 2. Don't use constructor lifecycle artifact injections, i.e. default constructors only. 3. Don't use Contextualizable. If you do, you need to dig deep into Merlin and see what legacy context entries it supports. 4. Use classname in the lookup() method, i.e. don't declare a key="" in the meta. Then both ECM and Merlin will lookup according to classname. That's all I can think of. Niclas ----- Original Message ----- From: "David Leangen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, August 28, 2004 5:35 AM Subject: Compatility issues > > I don't know if this is the right place to ask... > > But it appears to me that Cocoon is using Excalibur and not Merlin. Since I > plan to use some of my blocks with Cocoon, I am wondering what kind of > compatibility (or rather INcompatibility) issues I should expect to face. > > > Any hints would be much appreciated. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
