Thanks for confirming... 

-----Original Message-----
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 19, 2006 11:47 PM
To: axis-dev@ws.apache.org
Subject: Re: service lifecycle

Hi Tony;

Tony Dean wrote:

>Can someone answer this question for me...
>
>Since there appears to be a bug in startUp()... ie., the service is not fully 
>initialized by the time startUp() is called (AxisService.getFileName() returns 
>null). 
>
Pls create a JIRA for this , then I can fix that b4 next release (since at the 
moment we only fix the JIRAs ) .

> I was hoping to just avoid startUp() / shutDown() and just use init() / 
> destroy() since my service is using "application" scope.  Being that my 
> service is application scoped, there should only be one session created; 
> hence, init() / destroy() called only once.  It appears that init() is called 
> during service deployment which is good for me since the one-time 
> initialization that I am doing in init() will get executed before the first 
> actual service request.  I just wanted to confirm this behavior with the 
> experts since I do not want one-time initialization overhead to be added to 
> the first client's request.  Any comments?
>  
>
Yes , if you deploy the service in application scope then the init method will 
be called at the time when you deploy the service and not when it receive the 
first request.

>Thanks.
>-Tony
>
>Tony Dean
>SAS Institute Inc.
>919.531.6704
>[EMAIL PROTECTED]
>
>SAS... The Power to Know
>http://www.sas.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to