users@jax-rpc.java.net

Re: Sun JAX-RPC client against Axis JAX-RPC web service - problem with HttpSession

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Thu, 06 Oct 2005 09:21:32 -0700

Merten,
Thanks for the update.

Merten Schumann wrote:

>Some time ago I mentioned to have a problem with HTTP session
>maintenance, it worked when I used in my web service client the JAX-RPC
>implementation from Apache Axis but not with the one from Sun (J2EE 1.4
>RI).
>
>Just to mention: when I do use the Dynamic Invocation Interface Client
>approach instead of Dynamic Proxy Client, my JAX-RPC client CAN maintain
>the session with both JAX-RPC 1.1 implementations, from Sun and from
>Apache.
>
>So, still I could not find the reason why it does not work as expected
>with Sun JAX-RPC in the DP approach, anyway, I think I could switch to
>DII.
>
>Actually, I think I have switch to DII for some other reason too.
>Against rpc/enc and rpc/lit all of my clients (DII and DP, Sun or Axis)
>work fine. :-) My DII client works against wrapped/lit web service, my
>DP client not. Again, when I use the Axis JAX-RPC implemenation it
>works.
>
>Against doc/lit I could not get any of my JAX-RPC clients (DP or DII,
>Sun or Axis, AxisClient) working yet. :-(
>
>cu
> Merten
>
>
>
>>-----Original Message-----
>>From: Merten Schumann [mailto:Merten.Schumann_at_asg.com]
>>Sent: Thursday, June 30, 2005 1:52 PM
>>To: users_at_jax-rpc.dev.java.net
>>Subject: RE: Sun JAX-RPC client against Axis JAX-RPC web
>>service - problem with HttpSession
>>
>>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).
>>>>>
>>>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
>>For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
>For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>
>

-- 
 - Doug