On Sunday 18 April 2004 13:27, Aseem Bansal wrote:
Hi,
I am running into this error when my component act as both the service provider (simple sayHello service ) as well as an extension provider (implements LifecycleCreateExtension). In case it only act as creation extension provider or as a service provider, it works fine.
Stephen, is that allowed?
Honestly, never thought about it. I can see an issue concerning deployment ordering. While a lifecycle extension is a component, it is handled a little differently due to fact that it is providing support toward the establishment of other components. If at the same time its declaring itself as a service provider ... well - in principal that should be OK (but it seems a bit strange).
Because the LifeCycleExtension is to be part of the instantiation of the same component, there is a chicken/egg problem.
Only if the component declares a stage dependency on itself would be a little incestuous.
I believe that you can't do this, and _should_ not do it either, since IF you are a LifeCycle extension, you should not be a component...
I would agree!
Cheers, Stephen.
Cheers Niclas
--
|------------------------------------------------| | 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]
