[ 
https://issues.apache.org/jira/browse/AXIS2-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973719#action_12973719
 ] 

Afkham Azeez commented on AXIS2-4090:
-------------------------------------

Antonio,
Can you please resend the patch AXIS2-4090.patch? It is not compatible with the 
latest trunk. Sorry for taking so long to look at this.



> 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: 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 - After.jpg, 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]

Reply via email to