So, if I am stuck currently using ECM, then I need to keep it. Or, I guess if I think users of my wrapper are running it in ECM as well..
yes.
Any suggestions on what the best way to move forward? Deprecate the interface or something? Release two versions of the wrapper, one with and one without?
simply keep implementing Component in all your wrappers, but do move to use Servicable/ServiceManager. So:
class MyImpl implements My, Servicable, Component
{
service( ServiceManager sm )
{
MyOtherComp o = (MyOtherComp)sm.lookup( "blah" );
}
}that way, MyImpl won't suffer if the implementation for MyOtherComp has its 'Component' marker removed. And yes, this works in the latest release of ECM, too.
I guess, now that I grok the docs a bit better, that I am now supposed to use Serviceable and the ServiceManager in all the places I had Composable and ComponentManager? I guess my other question is whether to use upgrade Turbine's AvalonComponentService to use Fortress or Merlin. The overview doc (http://avalon.apache.org/containers/index.html) seems to suggest Fortress, however Merlin has a release out.
Fortress has a final release, merlin does not. The releases Steve is making available atm are snapshots of the Merlin3 tree, not final releases.
Based on my knowledge of the needs in turbine, I would suggest going with fortress if you decide to upgrade. Merlin atm offers a kitchen sink or two you guys don't need :D
cheers,
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
