[AXIS2-4091] WSDL11ToAxisServiceBuilder + HTTP Binding: Unused/Useless global element declations are appended into WSDL's XSD documents

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.4, nightly
• Component/s: kernel
• Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.83Ghz
• Assignee: Unassigned
• Reporter: Antonio Andrade
• Created: 16/Oct/08 19:10
• Updated: 26/Dec/17 13:55

Description

Observed Behavior:
1) New XML schema global elements declarations are created and appended into WSDL's XSD documents when they should not. This is the case of message <wsdl:part/>s already referencing global element declarations (through the 'element' attribute of the message part).

2) Whether a message part requires a 'wrapped' element or not can be determine by reading the 'wrappedInput' and 'wrappedOutput' attributes of the 'BindingOperationEntry' inner class after the message part has been analyzed but the 'addPartToElement' method fails to properly set them for all cases (i.e. ignores whether the message part comes from an input or output message by ignoring the 'isOutMessage' argument received).

Expected Behavior:
1) No XML schema global elements declarations should be added whenever message <wsdl:part/>s use the 'element' attribute (i.e. already reference global element declarations).

2) The 'addPartToElement' method should take into account the value of the 'isOutMessage' argument received to set the value of the 'wrappedInput' and 'wrappedOutput' attributes of the 'BindingOperationEntry' inner class.

Issue Links

• incorporates: AXIS2-4095 WSDL11ToAxisServiceBuilderTest: JUnit Tests for AXIS2-4071, AXIS2-4091 and AXIS2-4086
• is related to: AXIS2-4071 WSDL11ToAxisServiceBuilder + RPC/Literal OR HTTP binding =~ Inconsistent XMLSchema object: duplicated global element declarations