[jira] Commented: (CXF-2183) wsdl2java "only one global bindings customization is allowed" with embedded imported schema namespace

["Bob Fields (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701300#action_12701300 ] 

Bob Fields commented on CXF-2183:
---------------------------------

When the same wsdl is served up by the CXF servlet ?wsdl URL, the "globalBindings customization" error does not show up, but the specified bindings customization file is ignored. This is how I first noticed the problem - wsdl4j always embeds the imported schema, and it was ignoring the bindings. When I saved the URL contents locally, it gave a different error even though the wsdl was exactly the same as that from the CXF servlet. For this reason, the bug should probably be major instead of minor, because a client cannot use wsdl2java against a deployed webservice wsdl if using a bindings file, we have to send them the wsdl files manually.

> wsdl2java "only one global bindings customization is allowed" with embedded imported schema namespace
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2183
>                 URL: https://issues.apache.org/jira/browse/CXF-2183
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.1.4
>         Environment: CXF 2.1.4, JDK build 1.5.0_12-b04, Windows XP-64
>            Reporter: Bob Fields
>            Priority: Minor
>         Attachments: bindingsError.zip
>
>
> Error "WSDLToJava Error: Thrown by JAXB : only one globalBindings customization is allowed in a whole compilation" is returned when using a databinding xjb file against a wsdl with embedded referenced schema namespace. There is only one globalBindings customization, despite what the error says. The same wsdl2java process works fine when the schema is extracted to an external file and referenced in the wsdl through schemaLocation, no other difference in the bindings or wsdl2java parameters.
> Example attached: wsdl2.log shows the error. Bindings are meant to change XMLGregorianCalendar to Date. GregService.wsdl and GregService.xjb were generated by java2ws from working java code, and return the error. GregServiceA3.wsdl and .xjb work perfectly fine. The only difference in the wsdl files is:
> DOES NOT WORK
>    <xs:import namespace="http://valueobject.wdpr.com/" />
> ...
>   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
>    xmlns:tns="http://valueobject.wdpr.com/" attributeFormDefault="unqualified"
>    elementFormDefault="qualified" targetNamespace="http://valueobject.wdpr.com/">
>    <xs:element name="dates" type="tns:Dates" />
>    <xs:complexType name="Dates">
>     <xs:sequence />
>     <xs:attribute name="startDate" type="xs:date" use="required" />
>     <xs:attribute name="endDate" type="xs:date" use="required" />
>    </xs:complexType>
>   </xs:schema>
> WORKS
>         <xs:import namespace="http://valueobject.wdpr.com/" xmlns="http://www.w3.org/2001/XMLSchema"  schemaLocation="xsd/valueobject.wdpr.com.xsd"/>
> ...
> Same namespace information above in an external xsd/valueobject.wdpr.com.xsd schema file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.