[
https://issues.apache.org/jira/browse/AXIS2-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Andrade updated AXIS2-4090:
-----------------------------------
Attachment: AXIS2-4090.patch
Setting the value of both the operation MEP and message labels depending of the
'isServerSide' flag value.
Other: I think that the 'isServerSide' flag usage should be reviewed and a
general refactoring should be considered. i.e. There should probably be methods
defined in the WSDLToAxisServiceBuilder that deal with the retrieval of
isServerSide-sensitive information (messages based on directions, labels, etc)
in a more consistent way. The usage of this flag has caused a lot of
duplication of code
> 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.patch
>
> 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]
