[
https://issues.apache.org/jira/browse/AXIS2-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Andrade updated AXIS2-4090:
-----------------------------------
Attachment: JUnit Tests - Before.jpg
When 'isServerSide' is set to false, the XML schema elements associated with
the corresponding AxisMessages are either null or contain the opposite schema
element (i.e. input one when it should be ouput)
> WSDL11ToAxisServiceBuilder: Population of AxisBindingMessage and AxisMessages
> objects is inconsistent when the isServerSide flag is set to false
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4090
> URL: https://issues.apache.org/jira/browse/AXIS2-4090
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4, nightly
> Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.83Ghz
> Reporter: Antonio Andrade
> Attachments: AXIS2-4090-JUnitTests.patch, AXIS2-4090.patch, JUnit
> Tests - Before.jpg
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> Observed Behavior:
> Within the 'populateBinding' method, both the Message Exchange Pattern of the
> operation -axisOperation.getMessageExchangePattern()- and the message labels
> -WSDLConstants.MESSAGE_LABEL_XX_VALUE- depend on the 'isServerSide' flag but
> this dependency is ignored when the AxisBindingMessage and AxisMessage
> objects are being populated. This can be seen whenever the 'isServerSide'
> flag is set to 'false'.
> Expected Behavior:
> The value of both the operation's MEP and message labels should be retrieved
> taking into consideration the 'isServerSide' flag.
--
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]
