You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Francois Mireaux (JIRA)" <ji...@apache.org> on 2009/05/06 10:06:30 UTC
[jira] Updated: (AXIS2-4333) AxisError "ServiceContext in
OperationContext does not match" in some (complex ?) situations
[ https://issues.apache.org/jira/browse/AXIS2-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Mireaux updated AXIS2-4333:
------------------------------------
Attachment: AddressingBasedDispatcher.patch
A proposed patch
> AxisError "ServiceContext in OperationContext does not match" in some (complex ?) situations
> --------------------------------------------------------------------------------------------
>
> Key: AXIS2-4333
> URL: https://issues.apache.org/jira/browse/AXIS2-4333
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: modules
> Reporter: Francois Mireaux
> Attachments: AddressingBasedDispatcher.patch
>
>
> Trying to set up an Axis2 binding component for ServiceMix using Sandesha2, I sometimes have an AxisError "ServiceContext in OperationContext does not match", exception thrown by the MessageContext setOperationContext method. This method is called from AddressingBasedDispatcher just before calling setServiceContext : may be the error comes from Sandesha2 but eather the call of setServiceContext must be made first or there is no point in doing it, knowing how MessageContext.setOperationContext is written.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.