[
https://issues.apache.org/jira/browse/CXF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521307
]
maomaode commented on CXF-918:
------------------------------
Got this response from the JAX-WS mail list, just paste here:
The schema is correct. Having the same name with different types in wrapper
style, there is a collision. It cannot generate a java signature as per the
spec.
for e.g:
op(..., String theSameNameFieldDifferentDataType, int
theSameNameFieldDifferentDataType, ...) which would be incorrect in java.
Having the same type would generate a Holder for this.
op(..., Holder<String> theSameNameFieldDifferentDataType, ...)
There are many ways to get around this:
1. Use customization to change the name of the child elements
2. Disable wrapper style using customization. I hope there will be simple
command line option on wsimport in future versions.
3. Otherwise change the name of the child elements in schema
But, we should enhance the error message. Can you file a bug on this.
Jitu
> java code from wsdl2java for wrapped style if request and response have
> elements with the same names and different datatypes
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-918
> URL: https://issues.apache.org/jira/browse/CXF-918
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1, 2.1
> Environment: java 1.5.0_09
> Reporter: jmi
> Attachments: bug.wsdl
>
>
> wsdl2java renegares incorrect java code for some wsdls:
> wsdl uses "wrapped style" - request and response messages for operation, both
> have only one message-part. Each element referenced from message-part has
> different compex type, where both have multiple elements.
> Problem is if there are two elements, one in request, one in response
> datatype, where both have the same name, but they have different datatype. In
> such situation a Holder is generated, which holds dataype from response.
> Request parameter is lost.
> maybe reason is common with bug 907
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
