Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 93545 invoked from network); 27 Nov 2003 10:57:47 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Nov 2003 10:57:47 -0000 Received: (qmail 66245 invoked by uid 500); 27 Nov 2003 10:57:18 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 66083 invoked by uid 500); 27 Nov 2003 10:57:17 -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: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 66062 invoked from network); 27 Nov 2003 10:57:16 -0000 Message-ID: From: "Joan Pont" To: "'Steve Loughran'" , "'axis-dev@ws.apache.org'" Cc: "'gdaniels@apache.org'" , "'stevel@apache.org'" , "'st946tbf@drexel.edu'" Subject: RE: Bug#: 11815 ServiceLifecycle.destroy() never called when ses sion is destroyed Date: Thu, 27 Nov 2003 10:57:24 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3B4D5.3D24C21E" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3B4D5.3D24C21E Content-Type: text/plain Thanks Steve, Could you please explain in more detail your paragraph? as axis 1.2 is servlet2.3+, we dont need the housekeeping, we can use servlet lifecycle events, we just need someone to write the code and web.xml changes to do this. Does it mean that with Axis 1.2 if the user implements the code for servlet lifecycle event it will correctly call the sessionCreated/sessionDestroyed? How will this be done? Is there another way around so I can free session allocated resources when the session terminates from my MyServiceServiceBindingImpl class that is auto-generated by the Axis WSDL2Java emitter? When will axis 1.2 be out? Thanks, Joan. -----Original Message----- From: Steve Loughran [mailto:steve_l@iseran.com] Sent: 26 November 2003 22:58 To: Pont, Joan [MOP:GM12:EXCH] Cc: 'gdaniels@apache.org'; 'stevel@apache.org'; 'st946tbf@drexel.edu' Subject: Re: Bug#: 11815 ServiceLifecycle.destroy() never called when session is destroyed Joan Pont > Hi, > I've seen the problem with the ServiceLifecycle.destroy() never > being called when session is destroyed has been fixed. > > Is it possible to obtain the source code for that fix? Which > ones are the files involved? > Is there another way around so I can free session allocated > resources when the session terminates from my > MyServiceServiceBindingImpl class that is auto-generated by the Axis > WSDL2Java emitter? > > I need to know/be notified when a session has been terminated > within the Axis code. > Many thanks, > Joan. > I dont think a fix for this exists; I havent written a complete one, though had some old housekeeping code that could be used to trigger cleanup. as axis 1.2 is servlet2.3+, we dont need the housekeeping, we can use servlet lifecycle events, we just need someone to write the code and web.xml changes to do this. which is where, in the open source world, you come in. I would recommend you get on the Axis dev mail list, discuss this defect and work with people on the list (myself included), to get the fix into Axis1.2, which will be going out soon. -steve ------_=_NextPart_001_01C3B4D5.3D24C21E Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: Bug#: 11815 ServiceLifecycle.destroy() never called when = session is destroyed

Thanks Steve,
        Could you = please explain in more detail your paragraph?

as axis 1.2 is servlet2.3+, we dont need the = housekeeping, we can use
servlet lifecycle events, we just need someone to = write the code and
web.xml changes to do this.

        Does it = mean that with Axis 1.2 if the user implements the code for servlet = lifecycle event it will correctly call the = sessionCreated/sessionDestroyed? How will this be done?

       
        Is there = another way around so I can free session allocated resources when the = session terminates from my MyServiceServiceBindingImpl class that is = auto-generated by the Axis WSDL2Java emitter?

        When will = axis 1.2 be out?
Thanks,
Joan.


-----Original Message-----
From: Steve Loughran [mailto:steve_l@iseran.com] =
Sent: 26 November 2003 22:58
To: Pont, Joan [MOP:GM12:EXCH]
Cc: 'gdaniels@apache.org'; 'stevel@apache.org'; = 'st946tbf@drexel.edu'
Subject: Re: Bug#: 11815 ServiceLifecycle.destroy() = never called when session is destroyed

Joan Pont
> Hi,
>         = I've seen the problem with the ServiceLifecycle.destroy() never
> being called when session is destroyed has been = fixed.
>
>         = Is it possible to obtain the source code for that fix? Which
> ones are the files involved?
>         = Is there another way around so I can free session allocated
> resources when the session terminates from my =
> MyServiceServiceBindingImpl class that is = auto-generated by the Axis
> WSDL2Java emitter?
>
>         = I need to know/be notified when a session has been terminated
> within the Axis code.
> Many thanks,
> Joan.
>

I dont think a fix for this exists; I havent written = a complete one,
though had some old housekeeping code that could be = used to trigger
cleanup.

as axis 1.2 is servlet2.3+, we dont need the = housekeeping, we can use
servlet lifecycle events, we just need someone to = write the code and
web.xml changes to do this.

which is where, in the open source world, you come = in.

I would recommend you get on the Axis dev mail list, = discuss this defect
and work with people on the list (myself included), = to get the fix into
Axis1.2, which will be going out soon.

-steve

------_=_NextPart_001_01C3B4D5.3D24C21E--