Tuscany
  1. Tuscany
  2. TUSCANY-3859

tuscany generated wsdl: namespace prefix for the attribute "base" is missing

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Java-SCA-1.6.1
    • Fix Version/s: Java-SCA-1.x
    • Component/s: None
    • Labels:
      None

      Description

      I have a problem when I let tuscany generate the wsdl for a service.
      Namespace prefix for the attribute "base" is missing.

      If I have an object that extends another object, the schema generated
      should be:
      ...
      <xs:complexType name="myObjChild">
      <xs:complexContent>
      <xs:extension base="tns:myObj">
      ...

      but i got

      ...
      <xs:complexType name="myObjChild">
      <xs:complexContent>
      <xs:extension base="myObj">
      ...

        Activity

        Hide
        Simon Nash added a comment -

        This problem is related to the change for TUSCANY-3283, which fixes up "no namespace" type references in the schemas generated by JAXB.

        The fix for TUSCANY-3283 updates <xs:import> and <xs:element> schema elements, but doesn't update <xs:extension> elements. The fix is to add some code to update <xs:extension> elements as well.

        Show
        Simon Nash added a comment - This problem is related to the change for TUSCANY-3283 , which fixes up "no namespace" type references in the schemas generated by JAXB. The fix for TUSCANY-3283 updates <xs:import> and <xs:element> schema elements, but doesn't update <xs:extension> elements. The fix is to add some code to update <xs:extension> elements as well.
        Hide
        Simon Nash added a comment -

        Fixed in the 1.x trunk under revision r1091732.

        Show
        Simon Nash added a comment - Fixed in the 1.x trunk under revision r1091732.
        Hide
        Simon Laws added a comment -

        I believe this is fixed now as I applied the 1.x/TUSCANY-3298 fixes to 2.x and took the WSDL verify tests from 1.x and added them to the wsdlgen itest on 2.x.

        Show
        Simon Laws added a comment - I believe this is fixed now as I applied the 1.x/ TUSCANY-3298 fixes to 2.x and took the WSDL verify tests from 1.x and added them to the wsdlgen itest on 2.x.

          People

          • Assignee:
            Simon Nash
            Reporter:
            Antonio De Berardis
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development