AW: scope="soapsession" what causes destroy() to be called

upId after this time, it would not prevent that destroy() is triggered by this time-out; this however makes the used ServiceGroupId invalid and this is then sent as an exception back to the client; but the ServiceGroupId is valid only the time-out has occured. So th

AW: scope="soapsession" what causes destroy() to be called

with its initial request (it calls init() ( it's garanteed unique JSESSIONID and its garanteed unique ServicegroupId; But when I look at my log in AXP1>ty APACHE$SPECIFIC:[00]APACHE$JAKARTA_SERVER_OUTPUT.LOG/out=x.x I can find the following sequence of calls; and as you can se

scope="soapsession" what causes destroy() to be called

ns should becalled init(), login(), fktmap(), fktmap(), fktmap(), but the following functions are called in sequence destroy(), init(), login(), fktmap(), fktmap(), fktmap(), in bold the axis2 requierd functions one needs to implement for scope="soapsession" destroy() is the bad guy

RE: destroy

Hi, I didn't receive any response about that. Is this a bug? I close sessions manually and when I turn off Axis2, destroy method is called again so I got NPE because some elements I destroyed in that method were already destroyed. Thanks, Jorge Fernández Jorge Fernandez <[EMAIL P

Re: When is 'public void destroy(ServiceContext serviceContext) {...}' called?

Hi Jochen > Hello again, > > I got a little question concerning the method public void > destroy(ServiceContext serviceContext) inside a service-class. > > - When I have my service scope set to "request" - Is it right that > this Method will never be called? I ex

When is 'public void destroy(ServiceContext serviceContext) {...}' called?

Hello again, I got a little question concerning the method public void destroy(ServiceContext serviceContext) inside a service-class. - When I have my service scope set to "request" - Is it right that this Method will never be called? I expected it to be called whatever scope is s

destroy

are closed again. I have a method called logout that invokes destroy for cleaning axis2 session when the clients wants to close the session manually. How does Axis2 manage sessions? What may be happening here? Thanks, Jorge Fernández - Sé un Mejor Amant

[Axis2] Session "destroy(ServiceContext srvCtx)"-Method never called

Hi there I have a axis2-webservice implemented which has as scope "transportsession". In my service-class I have defined the "intit(ServiceContext serviceContext)" and the "destroy(ServiceContext serviceContext)" method. The init-Method is called well, if a

Re: init and destroy functions in an application scope axis2 service

Hi Gul > > I see init and destroy functions implemented in one of the samples > (servicelifecycle) in Axis2 distro. > > public void init(ServiceContext serviceContext) > public void destroy(ServiceContext serviceContext) throws AxisFault > > *When are these fun

init and destroy functions in an application scope axis2 service

I see init and destroy functions implemented in one of the samples (servicelifecycle) in Axis2 distro. public void init(ServiceContext serviceContext) public void destroy(ServiceContext serviceContext) throws AxisFault When are these functions get invoked for a service that is deployed as

ServiceLifecycle destroy() not called

I've implemented a simple service similar to what's listed below with the wsdd setting of Although I see that the ServiceLifecycle init() method is called each time a new session is created destroy() is never invoked upon session invalidation. Shortly after calling logout() which i