jax-ws
  1. jax-ws
  2. JAX_WS-538

<xs:list itemType="xs:QName"/> type to Java List<ItemType> mapping

    Details

      Description

      Consider having an XML Schema element definition like this:

      <element name="ParameterQNames" type="tns:ParameterQNameType" />
      <simpleType name="ParameterQNameType">
      <list itemType="xs:QName" />
      </simpleTpe>

      JAX-WS and JAXB use this correctly in WS message exchanges, but the generated
      WSDL looks like this:

      <xs:element name="ParameterQNames" nillable="true" type="xs:QName"/>

        Activity

        Hide
        jitu added a comment -

        Are you bundling the WSDL with your application? Then it won't publish a new
        WSDL. It publishes the bundled WSDL as it is.

        Show
        jitu added a comment - Are you bundling the WSDL with your application? Then it won't publish a new WSDL. It publishes the bundled WSDL as it is.
        Hide
        mdrescher added a comment -

        Bo, I lt it generate dynamically. No WSDL at all bundled.

        Show
        mdrescher added a comment - Bo, I lt it generate dynamically. No WSDL at all bundled.
        Hide
        jitu added a comment -

        I am suggesting that you should bundle WSDL since you seemed to have started
        from WSDL. There is no round-tripping: WSDL1->JAVA->WSDL2. WSDL1, and WSDL2
        will be different.

        Show
        jitu added a comment - I am suggesting that you should bundle WSDL since you seemed to have started from WSDL. There is no round-tripping: WSDL1- >JAVA ->WSDL2. WSDL1, and WSDL2 will be different.
        Hide
        mdrescher added a comment -

        Yes I noticed that with other stuff.

        However, so far the changes in WSDL were syntactically different, but
        semantically identical.

        This issue, however breaks the semantics of a list of QNames when the WSDL/XSD
        is generated from the correct Java representation List<QName>.

        Adding the WSDL would merely be a workaround that would only work for those that
        come from WSDL.

        Show
        mdrescher added a comment - Yes I noticed that with other stuff. However, so far the changes in WSDL were syntactically different, but semantically identical. This issue, however breaks the semantics of a list of QNames when the WSDL/XSD is generated from the correct Java representation List<QName>. Adding the WSDL would merely be a workaround that would only work for those that come from WSDL.
        Hide
        jitu added a comment -

        Can you attach a fromjava test case and the generated WSDL. Until, I am marking
        this one as incomplete

        Show
        jitu added a comment - Can you attach a fromjava test case and the generated WSDL. Until, I am marking this one as incomplete

          People

          • Assignee:
            jax-ws-issues
            Reporter:
            mdrescher
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: