e optimal to completely take out
any session information from the transport object and put it
elsewhere.
Original message
>Date: Tue, 01 Oct 2002 10:04:47 -0700
>From: Ricky Ho <[EMAIL PROTECTED]>
>Subject: Re: MessageContext.setMaintainSession
>To: [EMAIL PROTECTED]
&g
he HTTP cookies returned by the server. Most clients would either do this by default or require a flag to enable it like Axis clients do. As far as HTTP sessions go this is all you need to support them.
Alex
-Original Message-
From: Grant Echols (JanusLogix) [mailto:[EMAIL PROTECTED]]
Sent
- Original Message -
From: "Jan-Olav Eide" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 01, 2002 4:26 AM
Subject: RE: MessageContext.setMaintainSession
> So what you really are saying is that there is "less work" involved in
>
ur help. Your explanations
(especially about the client enabling sessions) made a big
difference.
Grant
- Original Message -
From:
Volanis, Alexander
To: '[EMAIL PROTECTED]'
Sent: Monday, September 30, 2002 4:05
PM
Subject: RE:
MessageContext.setMaintainSessi
On Tuesday 01 October 2002 13:26, Jan-Olav Eide wrote:
> So what you really are saying is that there is "less work"
> involved in setting up a non-axis non java client to use an
> axis-hosted web-service that its is for a java-axis client ? I
> find that a bit odd, but anyway...
Well, as long as
ite new
to AXIS (only read the book last night), so please forgive me if some of my
questions are not precise.
> -Original Message-
> From: Matthias Brunner [mailto:[EMAIL PROTECTED]]
> Sent: 1. oktober 2002 13:21
> To: [EMAIL PROTECTED]
> Subject: Re: MessageContext.setM
On Tuesday 01 October 2002 13:07, Jan-Olav Eide wrote:
> So I guess my question really is : What is the C# MS-SOAP
> equivalent of setMaintainSession ?
The MS SOAP Toolkit does this automatically (at least the high-level
handler), I guess it is the same with .net.
>
> In addition, a question r
> How does the handler detect the incoming request belongs to
> some existing sessions ?? (is it assessible via MessageContext ?) And
then
> throw a SOAP Fault if not.
I do that too with a login-service. The fact that a user is logged in is
maintained as state in the object that implements t
On Monday 30 September 2002 18:34, Ricky Ho wrote:
> How does the handler detect the incoming request belongs to some
> existing sessions ?? (is it assessible via MessageContext ?) And
> then throw a SOAP Fault if not.
The class which implements the service is loaded in session scope,
that mean
a SOAP client? Is this the extent of the session management in
Axis?
Thanks,
Grant
- Original Message -
From:
Volanis, Alexander
To: '[EMAIL PROTECTED]'
Sent: Friday, September 27, 2002 8:48
AM
Subject: RE:
MessageCont
sage -
From: "Ricky Ho" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 30, 2002 10:34 AM
Subject: Re: MessageContext.setMaintainSession
> How does the handler detect the incoming request belongs to some existing
> sessions ?? (is it assessible v
How does the handler detect the incoming request belongs to some existing
sessions ?? (is it assessible via MessageContext ?) And then throw a SOAP
Fault if not.
Rgds, Ricky
At 10:29 AM 9/30/2002 +0200, Matthias Brunner wrote:
>On Monday 30 September 2002 10:23, Jan-Olav Eide wrote:
> > > Whe
On Monday 30 September 2002 10:23, Jan-Olav Eide wrote:
> > When using HTTP cookies for session management the MS SOAP
> > library 3.0 supports this automatically. As for .net clients I
> > do not know but I think they will do the same.
>
> So what is the best way to gracefully detect and reject r
> When using HTTP cookies for session management the MS SOAP library
> 3.0 supports this automatically. As for .net clients I do not know
> but I think they will do the same.
So what is the best way to gracefully detect and reject requests from (MS
SOAP or Java) clients that are not session-ena
On Monday 30 September 2002 09:58, Jan-Olav Eide wrote:
> What about non-axis (or for that matter non-java, ie .Net clients)
> and session management ?
>
When using HTTP cookies for session management the MS SOAP library
3.0 supports this automatically. As for .net clients I do not know
but I t
Title: Message
What
about non-axis (or for that matter non-java, ie .Net clients) and session
management ?
-Original Message-From: Volanis, Alexander
[mailto:[EMAIL PROTECTED]]Sent: 27. september 2002
16:48To: '[EMAIL PROTECTED]'S
It's the server that has to initiate the session, not the
client. Make sure you're enabling session support when you're
deploying your services. To see if it works, snoop on your
calls using TCP monitor provided with Axis; you should see a
cookie send with the response from server, assuming you
is the extent of the session management in
Axis?
Thanks,
Grant
- Original Message -
From:
Volanis, Alexander
To: '[EMAIL PROTECTED]'
Sent: Friday, September 27, 2002 8:48
AM
Subject: RE:
MessageContext.setMaintainSession
The
correct way to enable
Title: Message
The
correct way to enable session management is in your deploy.wsdd file. Add
to your service deployment. To
get the desired effect your clients have to enable session management as well.
Use ((org.apache.axis.client.Stub) ws).setMaintainSession(true) where "ws" is
your serv
19 matches
Mail list logo
