turbine-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Siegfried Goeschl <siegfried.goes...@it20one.at>
Subject Re: Avalon component and avalon framework Startable interface
Date Fri, 01 Apr 2005 08:42:53 GMT
Hi Samuel,

I plainly don't know what's going on - I suggest that you fire up the 
debugger to see why the whole lifecycle is run ... :-)

Cheers,

Siegfried Goeschl

Samuel Le Berrigaud wrote:

>Hi Siegfried,
>
>I notice that too. And I used the code of the Torque Avalon Component
>to build my own. The only difference I see is that Torque avalon
>component also implements
>org.apache.avalon.framework.context.Contextualizable and 
>org.apache.avalon.framework.thread.ThreadSafe
>
>I think everything else is quite the same... and be sure I looked
>twice (even more) !
>
>SaM
>
>On Thu, 31 Mar 2005 15:49:40 +0200, Siegfried Goeschl
><siegfried.goeschl@it20one.at> wrote:
>  
>
>>Hi Samuel,
>>
>>what makes me wonder is that your service runs through the complete
>>lifecycle while you are still within the early initialization of
>>TurbineAvalonComponentService. You are also using the
>>TorqueAvalonService which does not show the same behaviour but
>>TorqueComponent also dumps debug messages when running through the
>>Avalon Lifecycle. So what is the difference in configuring/accessing
>>your service versus Torque?
>>
>>Cheers,
>>
>>Siegfried Goeschl
>>
>>Samuel Le Berrigaud wrote:
>>
>>    
>>
>>>Here is an extract of my logs. I have a log for each configure,
>>>initialize, start and stop methods...
>>>
>>>Tell me if you want more precision...
>>>
>>>SaM
>>>
>>>2005-03-31 09:38:39,780 [main] INFO
>>>apache.turbine.services.BaseServiceBroker - Start Initializing service
>>>(early): AvalonComponentService
>>>2005-03-31 09:38:40,618 [main] INFO
>>>turbine.services.avaloncomponent.TurbineAvalonComponentService -
>>>Lookup for Component org.apache.torque.avalon.Torque successful
>>>2005-03-31 09:38:41,014 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - configure()
>>>2005-03-31 09:38:41,049 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - initialize()
>>>2005-03-31 09:38:41,049 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - start()
>>>2005-03-31 09:38:41,049 [main] INFO
>>>notifier.engine.dialer.DialerManager - Starting the dialer manager...
>>>2005-03-31 09:38:41,052 [main] INFO
>>>notifier.engine.dialer.DialerManager - Started !
>>>2005-03-31 09:38:41,052 [main] INFO
>>>turbine.services.avaloncomponent.TurbineAvalonComponentService -
>>>Lookup for Component com.dexem.notifier.engine.dialer.avalon.Dialer
>>>successful
>>>2005-03-31 09:38:41,053 [main] DEBUG
>>>engine.dialer.avalon.DialerComponent - stop()
>>>2005-03-31 09:38:41,053 [main] INFO
>>>notifier.engine.dialer.DialerManager - Stopping the dialer manager ...
>>>2005-03-31 09:38:41,053 [main] INFO
>>>notifier.engine.dialer.DialerManager - Stopped !
>>>2005-03-31 09:38:41,053 [main] INFO
>>>apache.turbine.services.BaseServiceBroker - Finish Initializing
>>>service (early): AvalonComponentService
>>>
>>>On Thu, 31 Mar 2005 10:57:15 +0200, Siegfried Goeschl
>>><siegfried.goeschl@it20one.at> wrote:
>>>
>>>
>>>      
>>>
>>>>Hi Samuel,
>>>>
>>>>could you attach the debug output?!
>>>>
>>>>Cheers,
>>>>
>>>>Siegfried Goeschl
>>>>
>>>>Samuel Le Berrigaud wrote:
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>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: turbine-user-unsubscribe@jakarta.apache.org
>>>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>      
>>>
>>    
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>  
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message