> From: Gary Shea [mailto:[EMAIL PROTECTED]]
>
> I followed a bit of the Resolvable/Service/etc. debate, and am wondering
> if the outcome has made its way into Excalibur code yet.
The outcome made its way into the org.apache.avalon.framework.service
package. That's all there is for now.
> Any advice/hints?
If you can get away with it, *don't* use the newest conventions.
If you stick with Component / ComponentManager you have the ECM and
its associated classes. There is nothing similar for ServiceManager.
My advice is this: Stick with Component/ComponentManager. Once we
get around to Avalon 5, porting the code should be simple.
Of course, if you absolutely need to get rid of Component, go for
the service package.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
