Continued my investigations ... I changed my classpath now to take
JAX-RPC implementation from Axis (1.2.1) instead of the one from Sun
J2EE 1.4 ... And now my JAX-RPC client CAN maintain the session. Hmmmm.
cu
Merten
> -----Original Message-----
> From: Merten Schumann [mailto:Merten.Schumann_at_asg.com]
> Sent: Friday, June 24, 2005 9:21 AM
> To: users_at_jax-rpc.dev.java.net
> Subject: RE: Sun JAX-RPC client against Axis JAX-RPC web
> service - problem with HttpSession
>
> It's JSESSIONID, as expected.
> I've got the two logs from the HTTP traffic now. Well, the Axis client
> is sending back the cookie. The JAX-RPC client for some reason NOT.
> Hmmmm.
> Merten
>
> > -----Original Message-----
> > From: Kevin Jones [mailto:kevinj_at_develop.com]
> > Sent: Thursday, June 23, 2005 9:55 PM
> > To: users_at_jax-rpc.dev.java.net
> > Subject: RE: Sun JAX-RPC client against Axis JAX-RPC web
> > service - problem with HttpSession
> >
> > I'd be more interested in the name of the cookie. Is it
> > jsessionid (for
> > example)?
> >
> > Kevin Jones
> > http://kevinj.develop.com/weblog
> >
> > > -----Original Message-----
> > > From: Merten Schumann [mailto:Merten.Schumann_at_asg.com]
> > > Sent: 23 June 2005 13:30
> > > To: users_at_jax-rpc.dev.java.net
> > > Subject: RE: Sun JAX-RPC client against Axis JAX-RPC web
> > service - problem
> > > with HttpSession
> > >
> > > Used Axis tcpmon, thanx for the hint. Well, there seem to
> be really
> > > different cookies transferred for each request when I do
> > use my JAX-RPC
> > > client. When I do use a Axis client, the cookie is the
> > same, as expected
> > > (and needed).
>