As for #2, it seems wrong to have the management interface for a component exposed as one of its service interfaces. Is there a way to go from the ComponentModel of a component to a non-proxied reference without forcing the particular component to never be proxied? I'd like the CompositionListener to retrieve a reference directly to the component so it can create an MBean for the management interface, but still have the component able to be proxied when it is provided as a service to other components.
Assuming you are provided with the real instance - do you need to interact with the object? What I want to figure out is if we can handle this as a dynamic lifecycle extension (i.e. no stage dependency by the component, but the facility registers itself as a lifecycle extension and gets a reference to the object during deployment).
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]
