Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 22365 invoked from network); 31 Jul 2006 12:47:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 Jul 2006 12:47:44 -0000 Received: (qmail 39896 invoked by uid 500); 31 Jul 2006 12:47:37 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 39847 invoked by uid 500); 31 Jul 2006 12:47:37 -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 39836 invoked by uid 99); 31 Jul 2006 12:47:37 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jul 2006 05:47:37 -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.193 as permitted sender) Received: from [66.249.82.193] (HELO wx-out-0102.google.com) (66.249.82.193) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jul 2006 05:47:35 -0700 Received: by wx-out-0102.google.com with SMTP id s8so275651wxc for ; Mon, 31 Jul 2006 05:47:15 -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=bff8Zv6B35gKKq88so9kOym/k8Z/2Ntig7/yfoVfYku4o7elZuzRYzVCTVOTLd4vf80EMpOdXy/QiZU4HdKc1CLzI4rYDMiBwsNpfGb6Cdts09f3ZfMn3DJDFwhIB4UgyRs06f5RsHc1ZSVWYcO8McRk37A8ZBlnyKOq5XqD7/E= Received: by 10.70.87.1 with SMTP id k1mr2544997wxb; Mon, 31 Jul 2006 05:47:13 -0700 (PDT) Received: by 10.70.91.16 with HTTP; Mon, 31 Jul 2006 05:47:13 -0700 (PDT) Message-ID: <19e0530f0607310547l5f77b353h383cdd5a0783125e@mail.gmail.com> Date: Mon, 31 Jul 2006 08:47:13 -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: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 > > -- 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