hi,

despite of trying to understand the axis session example and various posts in the 
mailinglist i have been unable
to get my client application to work.

i have written a server, and enabled session mgmt. in the wsdd.
on the server side i access the session dependent data via 
MessageContext.getCurrentContext().getSession()

<deployment xmlns= ....
  ...
  <handler type="java:org.apache.axis.handlers.SimpleSessionHandler"
             name="SimpleSessionHandler" />
  <service name="SomeService" ...
    <requestFlow><handler type="SimpleSessionHandler" /></requestFlow>
    <responseFlow><handler type="SimpleSessionHandler" /></responseFlow>
    ...
  </service>
</deployment>

then i generated the client-side stubs out of the wsdd using 
org.apache.axis.wsdl.WSDL2Java
(the use of the Option -d Session does not seem to make a difference).

In my client code i try to activate session support again.
...
SomeServiceLocator someServiceLocator = new SomeServiceLocator();
SomeService service = someServiceLocator.getSomeService();
((Stub)service).setMaintainSession(true);

// Use someService

if i monitor the connection with the TCPMonitor utility it seems that the Server sends 
the
according Session Headers e.g.
...
<soapenv:Header>
  <ns1:sessionID xsi:type="xsd.long" 
xmlns:ns1="http://xml.apache.org/axis/session/";>-892127234322</ns1:sessionID>
</soapenv:Header>
...

unfortunately the clientside does not send back the session ID in the next request.

Can someone provide a very simple example of a client application that displays how to 
use Session Mgmt?

thanks in advance,
  alphonse bendt

Reply via email to