Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 18168 invoked from network); 23 Aug 2004 09:35:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Aug 2004 09:35:34 -0000 Received: (qmail 2908 invoked by uid 500); 23 Aug 2004 09:35:24 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 2864 invoked by uid 500); 23 Aug 2004 09:35:24 -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 2854 invoked by uid 99); 23 Aug 2004 09:35:23 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,MIME_HTML_NO_CHARSET X-Spam-Check-By: apache.org Received: from [195.243.210.197] (HELO mail4.telekom.de) (195.243.210.197) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 23 Aug 2004 02:35:20 -0700 Received: from U9JWN.mgb01.telekom.de by mail2.dmz.telekom.de with ESMTP for axis-dev@ws.apache.org; Mon, 23 Aug 2004 11:34:59 +0200 Received: from edmb003.edm-b.edm.dsh.de by U9JWN.mgb01.telekom.de with ESMTP for axis-dev@ws.apache.org; Mon, 23 Aug 2004 11:34:52 +0200 Received: by edmb003.edm-b.edm.dsh.de with Internet Mail Service (5.5.2657.72) id ; Mon, 23 Aug 2004 11:34:51 +0200 Message-Id: From: Dorner Thomas To: axis-dev@ws.apache.org Subject: AXIS Session problem Date: Mon, 23 Aug 2004 11:34:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C488F4.6F6E09E1" X-Virus-Checked: Checked 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_01C488F4.6F6E09E1 Content-Type: text/plain Hello all, I think I found a problem in AXIS. I do the following: I use the SimpleSessionHandler to handle Session, but I use the same Session over different Webservices. I set the Session over the AXISEngine.setOption(). But when I do this, for every new Service I call, there will be a new HTTPSession generated. When I understand the APIdoc the right way, my AXISSession depends on the HTTPSession. So when I use the AXISHTTPSessionListener to be notified, when my Session will be destroyed, I will be notified for every HTTPSession that will be destroyed. But in the end, when I call different Services, there is always one AXISSession, but a HTTPSession for every Service I call. So I will be notified for things that are not interesting for me. Am I right - or do I make a mistake? Thanks Tomi I use the Session for usermanagment - and should be notified when session ends, to destroy the subjet. ------_=_NextPart_001_01C488F4.6F6E09E1 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Hello all,

I think I found a problem in = AXIS.

I do the = following:

I use the SimpleSessionHandler to handle = Session, but I use the same

Session over different Webservices. I set the = Session over the AXISEngine.setOption().

But when I do this, for every new Service I = call, there will be a new HTTPSession generated.

When I understand the APIdoc the right way, = my AXISSession depends on the HTTPSession.

So when I use the AXISHTTPSessionListener to = be notified, when my Session will be = destroyed,

I will be notified for every HTTPSession that = will be destroyed.

But in the end, when I call different = Services, there is always one AXISSession,

but a HTTPSession for every Service I call. = So I will be

notified for things that are not interesting = for me.

Am I right – or do I make a = mistake?

Thanks Tomi

I use the Session for usermanagment – = and should be notified when session ends, to destroy the = subjet.

------_=_NextPart_001_01C488F4.6F6E09E1--