Uploaded image for project: 'Woden'
  1. Woden
  2. WODEN-214

WSDL-Viewer: Self-referencing element within a xsd:choice block circumvents anti-recursion

    Details

    • Type: Bug
    • Status: In Progress
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: M9
    • Fix Version/s: None
    • Component/s: Tools
    • Labels:
      None
    • Environment:
      Windows/Mozilla XSLT processors

      Description

      See the following block:

      <xsd:complexType name="SelfReferencingType">
      <xsd:choice>
      <xsd:element name="selfReference" type="tns:SelfReferencingType" minOccurs="0" maxOccurs="unbounded"></xsd:element>
      <xsd:element name="SomeOtherElement" type="xsd:string"/>
      </xsd:choice>
      </xsd:complexType>

      This somehow circumvents the anti-recursion strategy and causes the xslt processor to fail

        Activity

        Hide
        lmandel Lawrence Mandel added a comment -

        Tomi, do you have any time to investigate this issue with the WSDL viewer?

        Show
        lmandel Lawrence Mandel added a comment - Tomi, do you have any time to investigate this issue with the WSDL viewer?
        Hide
        tomi.vanek Tomi Vanek added a comment -

        The xsd:choice element was not handled in the XSLT.
        Attached is the patch for this issue.

        Show
        tomi.vanek Tomi Vanek added a comment - The xsd:choice element was not handled in the XSLT. Attached is the patch for this issue.
        Hide
        bgourlie W. Brian Gourlie added a comment -

        The patch appears to have broken the importing of external XSD's. This will cause MS XSLT processors to fail, in firefox the document will transform but imported types are not broken down and the imported source for each XSD is empty.

        Show
        bgourlie W. Brian Gourlie added a comment - The patch appears to have broken the importing of external XSD's. This will cause MS XSLT processors to fail, in firefox the document will transform but imported types are not broken down and the imported source for each XSD is empty.
        Hide
        bgourlie W. Brian Gourlie added a comment -

        Regarding my previous comment, Tomi's patch didn't introduce the XSD importing problem. The problem seems to have have been introduced in revision 61170.

        http://svn.apache.org/viewvc?view=rev&revision=611700

        Show
        bgourlie W. Brian Gourlie added a comment - Regarding my previous comment, Tomi's patch didn't introduce the XSD importing problem. The problem seems to have have been introduced in revision 61170. http://svn.apache.org/viewvc?view=rev&revision=611700

          People

          • Assignee:
            tomi.vanek Tomi Vanek
            Reporter:
            bgourlie W. Brian Gourlie
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development