[
https://issues.apache.org/jira/browse/AXIS2-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe updated AXIS2-3964:
-------------------------------------
Fix Version/s: (was: 1.5)
nightly
> WSDL20ToAxisServiceBuilder > HTTP Binding: AxisBindingMessage entry is being
> overwritten in corresponding AxisBindingOperation
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3964
> URL: https://issues.apache.org/jira/browse/AXIS2-3964
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.4.1
> Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.75Ghz
> Reporter: Antonio Andrade
> Assignee: Keith Godwin Chapman
> Priority: Minor
> Fix For: nightly
>
> Attachments: AXIS2-3964.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Observed Behavior:
> Within WSDL20ToAxisServiceBuilder, AxisBindingOperation children are always
> saved under the WSDLConstants.MESSAGE_LABEL_IN_VALUE key when the HTTP
> Binding is used. Look at processHTTPBindingExtention method (around line 921).
> Expected Behavior:
> When using the HTTP Binding, AxisBindingMessages should be saved under the
> corresponding key (should be correctly set into the corresponding
> AxisBindingOperation):
> - WSDLConstants.MESSAGE_LABEL_IN_VALUE whenever the message has a
> WSDLConstants.WSDL_MESSAGE_DIRECTION_IN direction
> - WSDLConstants.MESSAGE_LABEL_OUT_VALUE whenever the message has a
> WSDLConstants.WSDL_MESSAGE_DIRECTION_OUT direction
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
