[
https://issues.apache.org/jira/browse/CXF-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570789#action_12570789
]
Daniel Kulp commented on CXF-1020:
----------------------------------
I honestly thing the wsdl is invalid. The "stringHeader2" part definition
points to element="StringHeader". However, there is no element defined in the
target namespace of the wsdl. Thus, there is not type for it.
That said, we shouldn't be getting that far. Without "-exsh true", we
shouldn't be processing the out of band soap headers. It seems that for some
out of band headers on the output side, we are processing them even without the
flag set. I'm going to fix that.
> WSDL2Java tool error: failed to generate codes with
> twoHeadersSameNameDifferentNamespace
> ----------------------------------------------------------------------------------------
>
> Key: CXF-1020
> URL: https://issues.apache.org/jira/browse/CXF-1020
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Environment: windows.
> Reporter: Jeff Yu
> Assignee: Daniel Kulp
> Fix For: 2.1
>
> Attachments: headerDatatype.wsdl
>
>
> I am running WSDL2Java tool to generate codes, and then got the message as
> follow:
> WSDLToJava Error : Failed to create java parameter for part [stringHeader2]
> in method [twoHeadersSameNameDiffNS] - this wsdl is invalid, please use the
> wsdlvalidator tool to validate this wsdl
> I also run wsdlvalidator, it says valid WSDL, and I can get generated codes
> from JAXWS-RI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
