There are some answers in the AXIS FAQ : http://ws.apache.org/axis/faq.html#faq9
HTTP based sessions seem to be more standard than header based sessions. "In the JAX-RPC 1.0 version, the session management mechanisms require use of HTTP as the transport in the protocol binding." (see JAX-RPC specification). Frederic. > -----Message d'origine----- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Envoy� : mardi 4 mars 2003 15:56 > � : [EMAIL PROTECTED] > Objet : Managing Sessions > > > I have a SOAP server that connects to another evaluation > server that creates application level sessions, thereby > allowing the SOAP server to create multiple session > instances. I am writing a client that will initiate an > evaluation and will need some way of knowing what session it > connects to for subsequent requests to the session, since > more than one client may access the servers. Does anyone have > a good idea of how to deal with managing the sessions? Is it > feasible to pass session identifier information via the SOAP > header? If so, how would one do that? Otherwise, what other > ways can on manage session? BTW, I would prefer that session > management be transparent to the client. > > ________________________________ > Harry J. Kobetitsch > UBS Warburg > One North Wacker Drive > Chicago, Illinois 60606-2809 > 312-525-5866 > [EMAIL PROTECTED] > > Visit our website at http://www.ubswarburg.com > > This message contains confidential information and is intended only > for the individual named. If you are not the named addressee you > should not disseminate, distribute or copy this e-mail. Please > notify the sender immediately by e-mail if you have received this > e-mail by mistake and delete this e-mail from your system. > > E-mail transmission cannot be guaranteed to be secure or error-free > as information could be intercepted, corrupted, lost, destroyed, > arrive late or incomplete, or contain viruses. The sender therefore > does not accept liability for any errors or omissions in the contents > of this message which arise as a result of e-mail transmission. If > verification is required please request a hard-copy version. This > message is provided for informational purposes and should not be > construed as a solicitation or offer to buy or sell any securities or > related financial instruments. > >
