Deepal, I don't see a valid restriction for not being able to hot deploy an application scoped service.
Also, while we are on the topic of lifecycle, I tried out your fix for jira 730... that is, activation/deactivation of services from admin console. Unfortunately, my services destroy(ServiceContext), nor init(ServiceContext) are being called when I deactivate, or activate my service. I'm using July 18th snapshot. Thanks. -----Original Message----- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 19, 2006 12:21 AM To: axis-dev@ws.apache.org Subject: Re: hot deployment for services that have scope = "application" Hi Tony; Hmm, I just changed the code to throw that exception , at that time what I thought was when u deploying a service in application scope lifetime of both your service and system should be the same. So when the system start if you have any service with its scope being application , then I start those service and create ServiceContext for them too. I think we do not need to keep such a restriction , so I will go ahead and change the code not to throw exception. Tony Dean wrote: >Hi, > >Can you explain why you do not allow hot deployment of services that have >scope = "application". In the very least I should be able to drop a *new* >service into the services dir and it be automatically deployed. Do you not >agree? Maybe I am missing something here... Thanks. > >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]
