On Monday 19 January 2004 11:01, Stephen McConnell wrote:
Olaf Bergner wrote:
Are there any best practices for doing what I am trying to achieve? Currently, I am thinking about writing a lifecycle extension to that end. Is this a feasible solution? Or even better, does anybody have a working solution?
Take a look in merlin cvs.
1. Does it matter if the Service exposes add/remove listener methods?
Your not dealing with services with a model listener. What your dealing with is the ability to listen to the meta-model. This gives you total power and life and death. You can change component configurations, add components, remove component, register a runtime handler, i.e. totally change the meaning of reality.
2. Does the Listener explicitly know about the service producing the events?
The listener requests the root application model, registers itself of something as a listener to the model. Currently the only event it receives are composition events (model addition and removal). Moving forward this will be expanded to include events signaling changes to different model elements - like the classloader, or dependencies, or context models, etc. This way when a model event occurs - the model can determine the level of redeployment required to handle the change.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
