You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sanjiva Weerawarana <sa...@opensource.lk> on 2005/10/01 13:09:24 UTC

Re: [Axis2] Feedback on handlers and services

> On 9/30/05, Guy Pardon <gu...@atomikos.com> wrote:
> > Hi Axis team,
> >
> > We at Atomikos are using Axis (currently 1.2) to implement web service
> > transaction support.
> > However, I recently found out about the axis 2 architecture which seems
> > a good answer to all the problems we encountered with 1.2 (such as no
> > support for WS-Addressing, insufficient support for asynchronous
> > messaging etc).

Great .. any chance of you folks contributing to Kandula?
	http://ws.apache.org/kandula/

> > During our implementation of transaction handlers, we also found it to
> > be necessary that handlers have access to the same thread context that
> > will be used by the service implementation.
> > This is because the Java JTA binding of the WS-Transaction
> > specification will require this feature.
> > After going through the Axis2 documentation it is not yet clear if this
> > is  the case in Axis2 (it works in 1.2, though).

As Srinath pointed out, Axis2 does not switch threads in the default
message receivers. An message receiver which provides an async
programming model for the server could indeed switch but for the J2EE
integration case that will not be necessary.

Sanjiva.