[
https://issues.apache.org/jira/browse/AXIS2-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305648#comment-15305648
]
Andreas Veithen commented on AXIS2-5709:
----------------------------------------
Can you attach the WSDL and post the axis2-wsdl2code-maven-plugin configuration?
> Invalid wrapper tag name in request when using wrapped document/literal
> pattern in WSDL
> ---------------------------------------------------------------------------------------
>
> Key: AXIS2-5709
> URL: https://issues.apache.org/jira/browse/AXIS2-5709
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.6.2, 1.6.3
> Environment: JDK 1.7.0_71, OS MS Windows 7 SP1
> Reporter: Dmitriy Barbitov
> Labels: axis2-wsdl2code-maven-plugin, codegen, wsdl2java
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
