axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [Axis2] Making objects available on the response MessageContext (1.3-RC2) [SEC=UNCLASSIFIED]
Date Fri, 27 Jul 2007 01:08:50 GMT
Thank you Deepal, I have tested the fix and it seems to solve the problem 
we are having. 


Deepal Jayasinghe <> 
26/07/2007 06:14 PM
Please respond to


Re: [Axis2] Making objects available on the response MessageContext 


No need to create a JIRA , I fixed the issues and commit to both trunk
and the branch.


Deepal jayasinghe wrote:
> Hi
> please create a JIRA (if possible please attach test case as well).
> Thanks
> Deepal
>> Hello,
>> We have just upgraded our application to the new Axis2 1.3-RC2 version
>> to do some testing, but we're getting an exception. 
>> The exception is thrown in the application code, during a service
>> operation call.  It happens when a certain object can't be found on
>> the message context for a SOAP response - we have created an Axis2
>> response handler that expects this object to be there.
>> Currently before we calling the service operation we set this object
>> onto the Options object that we obtain from the ServiceClient.  In
>> Axis2 1.2, this seems to make the object available on the response
>> MessageContext for response handlers to access.  However in 1.3-RC2,
>> the object isn't available on the response MessageContext any more. 
>> I think that what we are doing (i.e. setting the object onto the
>> Options object to make it available to response handlers) is
>> incorrect, but it was working because of some code in Axis1.2 that has
>> since been refactored.  My question is: Is there a recommended way to
>> make objects available on the response MessageContext? (so they can be
>> accessed by response handlers). 

To unsubscribe, e-mail:
For additional commands, e-mail:

IMPORTANT:  This e-mail is intended for the use of the addressee and may contain information
that is confidential, commercially valuable or subject to legal or parliamentary privilege.
 If you are not the intended recipient you are notified that any review, re-transmission,
disclosure, use or dissemination of this communication is strictly prohibited by several Commonwealth
Acts of Parliament.  If you have received this communication in error please notify the sender
immediately and delete all copies of this transmission together with any attachments.

View raw message