ANNOUNCE: Apache Axis version 1.2.1 RELEASE

[Glen Daniels <gl...@thoughtcraft.com>]

Hi folks:

In the continued spirit of "release early and often", the Apache Axis team 
is pleased to announce the release of version 1.2.1, an incremental change 
over 1.2 final, with some added functionality and of course bug fixes.  You 
can find it at:

http://www.apache.org/dyn/closer.cgi/ws/axis/1_2_1/

A few words about this release -

* Changes can be found in changelog.html at the top level... Better cookie 
support, array handling, elementFormDefault in generated WSDL, SAAJ bug 
fixes, etc.

* As always, thanks to EVERYONE who submitted bug reports, patches, and
(especially) good, concise test cases.  Muchos gracias.

* Also as always, please send questions/comments to axis-user@ws.apache.org,
and development-related issues to axis-dev@ws.apache.org.  Issues may be
checked and filed at http://issues.apache.org/jira/browse/AXIS

Onwards to 1.2.Next...

Thanks,
--Glen
   on behalf of the Axis team

Concerning sessions

[Tom Ziemer <t....@dkfz-heidelberg.de>]

Hi everybody!

After browsing through the archive of this list and searching the web I 
am still no quite sure, which session approach to use for my services. 
What I need to do is quite simple - let a user authenticate, then only 
exchange a token/sessionid for all following calls. As far as I 
understand it, I have three alternatives:

Option a) Use a http session
Option b) Use SOAP headers
Option c) Reimplement basic session handling

Obviously c) is not the method of choice, so I am left to choose between 
a) and b). The most important issue for my web services is 
interoperability, since I am writing only the services but the clients 
will be implemented by another company and I have no idea what 
programming language/tools they are going to use.

Any input would be appreciated,

Tom