> From: Corey Jewett [mailto:[EMAIL PROTECTED]] > > >From Avalon-dev:
Please do not cross post messages from Avalon dev here. The focus of this list is to support the already released software. > 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(). Currently, the Fortress project is being groomed as ECM's replacement. It is functional, but it is changing. You will be able to use your existing components in Fortress--as long as you supply the appropriate meta data in the configuration files. Fortress ignores marker interfaces, and works with both Composable components and Serviceable components. > 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. Fortress is the proposed replacement for ECM. It is still being perfected, but you can easily migrate from ECM to Fortress by changing descriptor files. From that point on, it is just a question of changing your Composables to Serviceable as you have time. It is backwards compatible to provide a nice migration path. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
