Hi all, I moved from using Turbine 2.2 to Turbine 2.3.1 recently. I wanted to make use of the avalon component service for my own components.
One of my components needs to be started after configuring and stopped when the webapp application is undeployed. I so wanted to use the org.apache.avalon.framework.activity.Startable interface. The problem I have is that it seems that my component is stopped right after it is looked up by the avalon component service of Turbine... As anyone any idea of what I did wrong ? I tryed with the Disposable interface as well, but "dispose" is called a the exact same moment, right after "look up". Thanks for your help, SaM --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
