Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 87133 invoked from network); 2 Aug 2006 03:42:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Aug 2006 03:42:55 -0000 Received: (qmail 48354 invoked by uid 500); 2 Aug 2006 03:42:52 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 48316 invoked by uid 500); 2 Aug 2006 03:42:52 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 48303 invoked by uid 99); 2 Aug 2006 03:42:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2006 20:42:52 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates 66.249.82.202 as permitted sender) Received: from [66.249.82.202] (HELO wx-out-0102.google.com) (66.249.82.202) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2006 20:42:49 -0700 Received: by wx-out-0102.google.com with SMTP id s8so657484wxc for ; Tue, 01 Aug 2006 20:42:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TscYuMuo3wi3n/zSgswlWNZVOG4bB2K5rKHZmcHmyHMU/ivrnLYK2v7M8fiW/4hXPHCZU/sZU5y2gbTVblQCCcb//ehGnVZTmck+TFKJn7BWKOhP/MgipoBnl3+cJPPMro0IEx4ZzuEgAqgdenpROhiUrK4JjrqHbswoaeMJbVA= Received: by 10.70.133.19 with SMTP id g19mr591194wxd; Tue, 01 Aug 2006 20:42:28 -0700 (PDT) Received: by 10.70.91.16 with HTTP; Tue, 1 Aug 2006 20:42:27 -0700 (PDT) Message-ID: <19e0530f0608012042s77cc6b71o3fb1bab063b78799@mail.gmail.com> Date: Tue, 1 Aug 2006 23:42:27 -0400 From: "Davanum Srinivas" Reply-To: dims@apache.org To: axis-dev@ws.apache.org Subject: Re: [Axis] Load Web Service on Startup In-Reply-To: <44CF89FA.3050907@opensource.lk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <19e0530f0607310547l5f77b353h383cdd5a0783125e@mail.gmail.com> <44CF89FA.3050907@opensource.lk> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Deepal, I'd say it should be the following because there is no ServiceContext or MessageContext setup at startup time. init(ConfigurationContext) This is similar to servlets if you specify load-on-startup then "init(ServletConfig config)" is called. This would be a one time call only irrespective of scope. What do you think? -- dims On 8/1/06, Deepal Jayasinghe wrote: > I am not asking not to do this (I know this is a useful requirement), > but my problem is how do we solve this problem if service is deployed in > soapsession scope. > In that case we need to create new service instance for each soapsession > , so are we not in a problem ? > > of course we can create service instance and init that when system start > (irrespective of its scope), let's say we add a new method to service > impl what are the parameters we need to pass into that ? > > startUp(T1 t1, T2 t2){ > ????????????? > } > > > please comment on my questions , I need to solve those problem before > implementing this (then we can have this feature in Axis2 1.1) > > -Deepal > > Davanum Srinivas wrote: > > > Tony, > > > > I am with you on this. There should be a way to do this. > > > > -- dims > > > > On 7/31/06, Tony Dean 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:deepal@opensource.lk] > >> Sent: Friday, July 28, 2006 12:04 PM > >> To: axis-dev@ws.apache.org > >> 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:deepal@opensource.lk] > >> >Sent: Friday, July 28, 2006 2:18 AM > >> >To: axis-user@ws.apache.org > >> >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 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 > >> >>>> > >> >>>>ronak.patel@baesystems.com > >> >>>> > >> >>>> > >> >>>> > >> >>>-- > >> >>>Thanks, > >> >>>Deepal > >> >>>................................................................ > >> >>>~Future is Open~ > >> >>> > >> >>> > >> >>> > >> >>>--------------------------------------------------------------------- > >> >>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > >> >>>For additional commands, e-mail: axis-user-help@ws.apache.org > >> >>> > >> >>> > >> >>> > >> >>> > >> >> > >> >> > >> > > >> >-- > >> >Thanks, > >> >Deepal > >> >................................................................ > >> >~Future is Open~ > >> > > >> > > >> > > >> >--------------------------------------------------------------------- > >> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > >> >For additional commands, e-mail: axis-user-help@ws.apache.org > >> > > >> > > >> >--------------------------------------------------------------------- > >> >To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > >> >For additional commands, e-mail: axis-dev-help@ws.apache.org > >> > > >> > > >> > > >> > > >> > > >> > >> -- > >> Thanks, > >> Deepal > >> ................................................................ > >> ~Future is Open~ > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > >> For additional commands, e-mail: axis-dev-help@ws.apache.org > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > >> For additional commands, e-mail: axis-dev-help@ws.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-dev-help@ws.apache.org > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org