[
https://issues.apache.org/jira/browse/AXIS2-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Gallardo resolved AXIS2-2091.
----------------------------------
Resolution: Fixed
Fixed in rev 503847.
> Callback.onError() faults should be delivered with a MessageContext
> -------------------------------------------------------------------
>
> Key: AXIS2-2091
> URL: https://issues.apache.org/jira/browse/AXIS2-2091
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Nick Gallardo
> Assigned To: Nick Gallardo
> Attachments: patch.txt
>
>
> When Axis2 delivers a fault message via the Callback.onError() method, it
> delivers just the fault or exception object with no other additional data.
> For sync cases, we are able to get the MessageContext for the fault response
> from the OperationClient and then go down the fault processing chain for
> JAX-WS. We need this same capability for async cases as well so that similar
> fault processing can occur.
> This can be addressed by changing the AxisFault that's already being
> delivered to be constructed with the MessageContext inside of it. The APIs
> already exist to store the MessageContext on the fault, we just need to make
> the callback delivery code make use of it. This can be done with a slight
> change to org.apache.axis2.util.Util.getInboundFaultFromMessageContext().
> The other change that needs to be made is to the
> OutInAxisOperation.NonBlockInvocationWorker. The way the fault is
> constructed there is not symmetric with the way it's being done in the
> CallbackReceiver. This code needs to be changed to mirror the
> CallbackReceiver's implementation.
> I'm working on a patch and should have something posted shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
