[
https://issues.apache.org/jira/browse/CXF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521302
]
maomaode commented on CXF-918:
------------------------------
Oh, i see the difference now, it's the same name but different type.
Seems a problem in wsdl2java, however i checked with the jaxws ri, but said the
wsdl is "error: uniqueness constraint violation", means the same name but
different type is not allowed, but i can not find any reason for it. have sent
a mail to jaxws, let see what the answer is, if that is the case, then I'll
check the schema and report the same error, otherwise, I'll fix it like what
you said.
> 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.
