The
ServiceLifeCycle interface works fine with Axis.
Olivier Brand
-----Original Message-----
From: Nirmal Mukhi [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 6:07 PM
To: [EMAIL PROTECTED]
Subject: Re: ServiceLifecycle in wsif ???
Hi,
No, there is no notion of a lifecycle, though I can see why it makes sense. For now you can expose such things as application-level operations - maybe have a standard "lifecycle port type" exposed by each service. then you can bind these operations to appropriate binding-specific things, such as ejbCreate/ejbRemove for EJBs, etc.
But I think it's a good idea to define binding independent lifecycle methods on the service class, similar to the JAX RPC serviceLifecycle interface and supporting that in the providers. For java and EJBs this should be straightforward but the SOAP case is a little hard since AFAIK the JAX RPC serviceLifecycle interface isn't supported by Axis which is what our default SOAP provider uses. If you care to do some work on this and send us the code that would be cool :-)
Thanks,
Nirmal.
"Brand, Olivier" <[EMAIL PROTECTED]> 03/21/2003 04:45 AM
Please respond to wsif-user
To: <[EMAIL PROTECTED]>
cc:
Subject: ServiceLifecycle in wsif ???
I do have the following question:
Is there the notion of the jaxrpc servicelifecycle in wsif for all implemented providers ?
For instance I would like to initialize some objects at startup. My guess would be to use the underlying capability of the technology used:
- ServiceLifeCycle interface for SOAP
- constructor for Java
- ejbCreate / ejbRemove for EJB
Is that assumption correct ?
Olivier Brand
Senior Java Architect - Mobile Services and Integration
Global IT & Technology Management
Vodafone AG
Mannesmannufer 3 - 40213 Dusseldorf - Germany
Mobile: +49 172 2094646
E-Mail: [EMAIL PROTECTED]
