I'm using cookies (seems to be the default in Axis), and I can see
the set-cookie instruction in the HTTP response (using TCPMonitor):
> Set-Cookie: jsessionid=3029091017259021561;path=/

So far, yes, that's also my only clue: that .Net may use a
different cookie... But anyway, they should simply store and
re-send *all* the presented cookies! (sigh...)

My setup is only client-side, so I can't test and see what
cookie name is used by a .Net service...

Thanks for forwarding to the interop group.

-- Oliver

Glen Daniels wrote:
> 
> Hi Oliver!
> 
> Do you know how .NET does sessions?  Axis has two approaches - one with HTTP 
>cookies, and another with SOAP headers.  .Net certainly wouldn't support the SOAP 
>header version out of the box, and I doubt that the cookies we use would match the 
>ones they use (if they do).  I just sent a message to soapbuilders about this very 
>issue, so we'll see what comes back out of that conversation.
> 
> --Glen
> 
> > -----Original Message-----
> > From: Oliver Suciu [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 27, 2002 5:51 PM
> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: .Net-Axis sessions?
> >
> >
> > Hi all,
> >
> > Has anybody managed to get a .Net client talk to an Axis service,
> > using a session context?
> >
> > I've got an Axis (beta1) web service talking successfully
> > with both an Axis and a .Net (beta2, C#) client.
> >
> > I've also added session management on the server side:
> >  - MessageContext.getCurrentContext().getSession()
> >
> > This works well with the Axis client:
> >  - TestSvcServiceLocator.setMaintainSession(true)
> >
> > However, with the .Net client, no session is established,
> > even with:
> >  - TestSvcService ts = new TestSvcService();
> >  - ts.CookieContainer = new CookieContainer();
> >
> > Any clue?
> >
> > Thanks a lot,
> >
> > -- Oliver
> >

Reply via email to