Hi Brian;

Handlers are stateless across multiple invocations. You should store
the states in the OperationContext (msgctx.getOperationContext()). Get
back if that do not solve your problem.

Thanks
Srinath

On 1/31/06, Brian Shields <[EMAIL PROTECTED]> wrote:
> Hello,
> When using the same handler for inflow and outflow messages, does axis2
> create a seperate object of the handler for the different flow. It uses
> the same object for all inflows, but is there a second object for all
> outflow messages? It is confusing as the two instances of the handler
> (if there are two instances) have the same object hashCode, yet when
> using a java collection object within the handler, the outflow cannot
> see the same collection object as the inflow?? Any suggestions?
>
> --
> Brian Shields BSc. MSc.,
> PhD Candidate,
> Department of Information Technology,
> National University of Ireland,
> Galway,
> Ireland.
>


--
============================
Srinath Perera:
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani

Reply via email to