[AXIS2-3964] WSDL20ToAxisServiceBuilder > HTTP Binding: AxisBindingMessage entry is being overwritten in corresponding AxisBindingOperation

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.4.1
• Component/s: kernel
• Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.75Ghz
• Assignee: Unassigned
• Reporter: Antonio Andrade
• Created: 06/Aug/08 01:22
• Updated: 26/Dec/17 13:41

Description

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

Issue Links

• is related to: AXIS2-4090 WSDL11ToAxisServiceBuilder: Population of AxisBindingMessage and AxisMessages objects is inconsistent when the isServerSide flag is set to false
• relates to: AXIS2-4090 WSDL11ToAxisServiceBuilder: Population of AxisBindingMessage and AxisMessages objects is inconsistent when the isServerSide flag is set to false