[AXIS2-5710] Invalid wrapper tag name in request when using wrapped document/literal pattern in WSDL

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.6.2, 1.6.3
• Component/s: codegen
• Labels: axis2-wsdl2code-maven-plugin wsdl2java
• Environment: JDK 1.7.0_71 x64, OS MS Windows 7 sp1 x64
• Assignee: Unassigned
• Reporter: Dmitriy Barbitov
• Created: 23/Jul/15 11:02
• Updated: 18/Apr/16 22:46
• Resolved: 18/Apr/16 22:46

Description

When using wrapped document/literal pattern in WSDL, requests, sent by the client, generated using WSDL2Code, can have invalid letter case in the request's wrapper tag name.

We have a WSDL file containing an opertaion with document/literal style. This opertaion uses "wrapped" pattern, as described here: http://www.ibm.com/developerworks/library/ws-usagewsdl/index.html. The name of the operation has first capital letter.

We generate client code from this wsdl, using WSDL2Java or axis2-wsdl2code-maven-plugin.

When we try to use generated code to call the service, we get invalid soap request, having wrapper tag name starting from the lowercase letter (e.g., if an operation name is "GetUsers", we get a wrapper tag named "getUser").

We have dived into the source code of axis2-codegen and have found the cause of that bug. InterfaceImplementationTemplate.xsl (from the org.apache.axis2.wsdl.template.java package) in several places uses java-styled operation name instead of original operation name from WSDL (lines 101, 361, 370, 377, 378).

Issue Links

• duplicates: AXIS2-5709 Invalid wrapper tag name in request when using wrapped document/literal pattern in WSDL