> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > > > How about Recomposable, Recyclable, etc? > You mean that they are there but the call times are container > specific? I think I agree.
Recyclable is an extension to the ECM container, and it not supported in any other container. It is not part of the core framework. The Recomposable, Reconfigurable, Reparameterizable, and Recontextualizable interfaces are defined, but few if any containers actually support them at this time. It has always been the intention, but we haven't gotten to that level yet. I wanted to get there with Fortress--but I didn't have time to implement the ConfigurationManager (that automatically reloads configuration files and works with containers to notify when to update the component. Now, that said, I believe that both the ComponentLocator (CM in A4) and the Context can easily be managed by the container without explicitly telling the component that things have changed. The only time those are necessary is if you lookup your components at init time. If the components are resolved at runtime, you do not need Recomposable. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
