[
https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian DePradine resolved AXIS2-2301.
------------------------------------
Resolution: Fixed
Fix Version/s: nightly
> wsa 04 version problem - AxisFault Required MessageID in header in Response
> ---------------------------------------------------------------------------
>
> Key: AXIS2-2301
> URL: https://issues.apache.org/jira/browse/AXIS2-2301
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.1.1
> Reporter: Gee Chia
> Assigned To: Brian DePradine
> Fix For: nightly
>
>
> A Web service request worked in wsa 1.0 but failed in wsa 04 with
> AxisFault: A required message information header, To, MessageID, or Action,
> is not present. Basically, message ID was not set in MessageContext for a
> Response was the cause of the AxisFault.
> The exception was thrown from the checkForMandatoryHeaders method in the
> org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler.
> As I understood from the code
> inspection,AbstractInOutSyncMessageReceiver::receive() method invokes
> MessageContext outMsgContext =
> MessageContextBuilder.createOutMessageContext(msgContext);
> The messageID is conditionally set in the outMsgContext.
> Then later on, it failed with messageID not set fault.
> The same transaction/request worked in wsa 1.0. It worked because
> AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action
> only.
> My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2
> 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1.
--
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]
