>From Avalon-dev: On Tue, 2002-06-25 at 01:44, Peter Donald wrote:
<snip> > >But if Avalon is used we're > >using one version. What if a user of FOP someone wants/needs to use a > >different version of Avalon? > > If A5 eventuates it will be possible via a compatability layer so in theory > all should be good. However to ensure this is the case I would encourage > you to; > * Use ServiceManager interface rather than ComponentManager (And don't use > Component marker interface) > * Use LogEnabled rather than Loggable to aquire Loggers > * Don't use ServiceManager.release() > > If you do the above then everything should be forward compatible. One thing > you may want to also do if you can is avoid the marker interfaces like > ThreadSafe etc. > Being a newbie I'm somewhat concerned about the work I'm doing now being applicable to future framework revisions. I'm using ECM and liberally using ComponentManager, the Component interface, and ComponentManager.release(). If these are going away (at least in a fashionable sense) what then should I be doing (besides the aforementioned) to be better prepared for A5? Should I be replacing ECM with something else? Phoenix? Please advise. Thanks, Corey -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
