This is a feature I too would use. Another important reason is that in many services, this initialization is based on configuration paramters. It'd be nice to see the initialization occur at service startup, so that any errors are discovered at that point, versus a failed client request. -Dave
-----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Monday, July 31, 2006 8:47 AM To: [email protected] Subject: Re: [Axis] Load Web Service on Startup Tony, I am with you on this. There should be a way to do this. -- dims On 7/31/06, Tony Dean <[EMAIL PROTECTED]> wrote: > I will deploy my service in "application" scope because I want to have only one instance of my service running. > > The idea of "load on startup" is the same principle used by a servlet. You set an option so that when the container starts your application is also started. Otherwise, your application is started on demand when the first request is sent. This will make the first request slower than the rest. > > I can live with that, but why should we? > > -----Original Message----- > From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] > Sent: Friday, July 28, 2006 12:04 PM > To: [email protected] > Subject: Re: [Axis] Load Web Service on Startup > > I think we are trying to make the simple thing harder by adding a number of options, therefore I am 0- on adding a new option. > > Let's say we agree to do this , when we initialize the service implementation class what should we pass into that method ? if the answer is ServiceContext then we are going to have problems. > > btw I need to clarify one more thing (I think I am missing something), do you want to deploy your service in scope other than application and you want to have only one instance of service implementation class ? > > Thanks > Deepal > > > > Tony Dean wrote: > > >I think users will want an option (load-on-startup=on|off) to either load scope="application" services on container startup or upon the first request. I personally would want my service loaded and ready to go before the first request is issued. Users will certainly be willing to take the hit waiting for the container to initialize rather than during a real-time request. > > > >-Tony > > > >-----Original Message----- > >From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] > >Sent: Friday, July 28, 2006 2:18 AM > >To: [email protected] > >Subject: Re: [Axis] Load Web Service on Startup > > > >yes if you deploy the service in application scope , o.w when it get the first request. > > > >Davanum Srinivas wrote: > > > > > > > >>Deepal, > >> > >>The question is: Do we call init(ServiceContext) when tomcat starts > >>up OR when we get the first request for that service. > >> > >>People want to do the latter, to avoid taking a hit (slow-ness) on > >>the first request. > >> > >>thanks, > >>dims > >> > >>On 7/28/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > >> > >> > >> > >>>In Axis2 > >>> > >>>adding following method to serviceImpl class you can achieve you > >>>goal, so if you serviceimpl class look like ; > >>> > >>>public class Myservice{ > >>> > >>>public void init(ServiceContext sc){ // write initialization code > >>>here } > >>> > >>>} > >>> > >>> > >>> > >>> > >>>Patel, Ronak (US SSA) wrote: > >>> > >>> > >>> > >>>>Hello All, > >>>> > >>>>I am interested in finding out how I can force Apache Axis to load > >>>>and run my Web Service (by calling it's init() method) when the > >>>>Web Server starts. > >>>> > >>>>Is there a configuration parameter that I need to set somewhere? > >>>> > >>>>I am interested in finding this out in both Axis2 and Axis1.x. > >>>> > >>>>Any help would be greatly appreciated. > >>>> > >>>>Ronak Patel > >>>> > >>>>Software Engineer > >>>> > >>>>BAE Systems CNIR > >>>> > >>>>450 Pulaski Road > >>>> > >>>>Greenlawn, NY 11740 > >>>> > >>>>(631) 262 - 8230 > >>>> > >>>>[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >>>> > >>>> > >>>> > >>>-- > >>>Thanks, > >>>Deepal > >>>................................................................ > >>>~Future is Open~ > >>> > >>> > >>> > >>>------------------------------------------------------------------- > >>>-- To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >>> > >> > >> > > > >-- > >Thanks, > >Deepal > >................................................................ > >~Future is Open~ > > > > > > > >--------------------------------------------------------------------- > >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] > > > > > > > > > > > > -- > Thanks, > Deepal > ................................................................ > ~Future is Open~ > > > > > --------------------------------------------------------------------- > 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] > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- 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]
