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 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
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 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 -- Brian Shields BSc. MSc., PhD Candidate, Department of Information Technology, National University of Ireland, Galway, Ireland.
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 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 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) iD8DBQFD33mrjON2uBzUhh8RAqZRAKCVhs22wm+y3Li53GXGhqdOs2R1xwCgqeo0 C3/4iz1DlcUzrSgbZSShfeQ= =PZnG -END PGP SIGNATURE-
