Axis2 client that works with jax-ws handlers add Jax-ws handlers to Axis2 Client

Hi Every one, i am new for Axis2, my question here is Axis2 client that works with jax-ws handlers. how to add jax-ws handlers for Axis2 Client. i have Axis2 Client for this i need to add jax-ws handlers. i spend lot of time to find out the solution, my bad ness i didnt get any posts

[Axis2] Dynamic registration of handlers with Axis2/Rampart

The following test code registers a callback handler in order to add a username token to the outgoing SOAP message. My question is how this could be achieved when using Axis2 and Rampart. The Axis2 API is quite different to Axis, and all the examples I can find revolve around the existence of a

Handlers in Axis2

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

Re: Handlers in Axis2

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

Re: Handlers in Axis2

Thanks Srinath, using the OperationContext I can persist object state between the request and the reply. Regards, Brian. Srinath Perera wrote: Hi Brian; Handlers are stateless across multiple invocations. You should store the states in the OperationContext (msgctx.getOperationContext()). Get

Re: Handlers in Axis2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brian, Small clarification. OperationContext is not only for request-response (In-Out). It is per MEP. But for the time being we support InOut and In only MEPs. - -- Chinthaka Brian Shields wrote: Thanks Srinath, using the OperationContext I