You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "John Hite (JIRA)" <ji...@apache.org> on 2008/08/28 17:36:45 UTC

[jira] Created: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Nillable schema elements in WSDL cause XmlSchemaException
---------------------------------------------------------

                 Key: CXF-1769
                 URL: https://issues.apache.org/jira/browse/CXF-1769
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 2.1.2
            Reporter: John Hite
         Attachments: HelloWorld.wsdl

A WSDL with a nillable schema element, e.g.

<element name="sayHelloResponse">
   <complexType>
    <sequence>
     <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
    </sequence>
   </complexType>
  </element>

can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:

"org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"


Steps to reproduce:

1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.

If you remove the 'nillable="true"' from the wsdl, then this error goes away.


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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment:     (was: HelloWorld.wsdl)

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment: HelloWorld.wsdl

WSDL that caused the problem

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Comment: was deleted

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Description: 
A WSDL with a nillable schema element, e.g.

<element name="sayHelloResponse">
   <complexType>
    <sequence>
     <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
    </sequence>
   </complexType>
  </element>

can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:

"org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld"


Steps to reproduce:

1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.

If you remove the 'nillable="true"' from the wsdl, then this error goes away.


  was:
A WSDL with a nillable schema element, e.g.

<element name="sayHelloResponse">
   <complexType>
    <sequence>
     <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
    </sequence>
   </complexType>
  </element>

can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:

"org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"


Steps to reproduce:

1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.

If you remove the 'nillable="true"' from the wsdl, then this error goes away.



> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment:     (was: HelloWorld.wsdl)

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Resolved: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-1769.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.3
                   2.0.9
         Assignee: Daniel Kulp  (was: Benson Margulies)


I added some code to the jaxb databinding on trunk to workaround a bug in JAXB for this.   That's why it's working there.

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>            Assignee: Daniel Kulp
>             Fix For: 2.0.9, 2.1.3
>
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment: build.xml

Ant buildfile. Shows the commands that were executed to produce this problem.

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment: HelloWorld.wsdl

The WSDL that causes problems

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Attachment: HelloWorld.wsdl

WSDL that caused the problem.

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Assigned: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies reassigned CXF-1769:
-------------------------------------

    Assignee: Benson Margulies

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>            Assignee: Benson Margulies
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Updated: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "John Hite (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Hite updated CXF-1769:
---------------------------

    Comment: was deleted

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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

[jira] Commented: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627242#action_12627242 ] 

Benson Margulies commented on CXF-1769:
---------------------------------------

This seems to work on the trunk. Note that I do not include the specific version of JAX-WS that you include when I try it.

> Nillable schema elements in WSDL cause XmlSchemaException
> ---------------------------------------------------------
>
>                 Key: CXF-1769
>                 URL: https://issues.apache.org/jira/browse/CXF-1769
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.2
>            Reporter: John Hite
>            Assignee: Benson Margulies
>         Attachments: build.xml, HelloWorld.wsdl
>
>
> A WSDL with a nillable schema element, e.g.
> <element name="sayHelloResponse">
>    <complexType>
>     <sequence>
>      <element name="output" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true" />
>     </sequence>
>    </complexType>
>   </element>
> can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown:
> "org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld"
> Steps to reproduce:
> 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL.
> 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend.
> If you remove the 'nillable="true"' from the wsdl, then this error goes away.

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