Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <15124409.1186456440059.JavaMail.jira@brutus>
Date: Mon, 6 Aug 2007 20:14:00 -0700 (PDT)
From: "Paul Hanke (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
 on complex XML schemas
In-Reply-To: <20461646.1184892186301.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CXF-815?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel#action_12518059 ]=20

Paul Hanke commented on CXF-815:
--------------------------------

I have reported the issue of the invalid schemas to the OSS/J team - sorry =
to have bothered you guys with this! :-(

> wsdl2java compiler gets stuck in a loop on complex XML schemas
> --------------------------------------------------------------
>
>                 Key: CXF-815
>                 URL: https://issues.apache.org/jira/browse/CXF-815
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.0-RC, 2.0
>         Environment: Java 1.5; Windows 2003; VMware Workstation 5.5
>            Reporter: Paul Hanke
>            Assignee: jimma
>            Priority: Minor
>         Attachments: ossj-wsdl.zip
>
>
> wsdl2java compiler gets stuck in a loop on complex XML schemas.  Compiled=
 the WSDL for the OSS/J Common API just fine.  This WSDL imports a single f=
lat XSD.  Next, I took the Common API WSDL as a template and started writin=
g a WSDL for the OSS/J Trouble Ticket API.  This WSDL imports an XSD which =
in turn imports other XSDs which in turn import other XSDs and so on (some =
XSDs are multiply imported in this dependency graph).  When I tried compili=
ng the Trouble Ticket WSDL, the WSDL compiler started eating up 99% of the =
CPU (the memory footprint stayed steady at roughly 50M) and showed no signs=
 of stopping (I eventually terminated the process).  I modified the Trouble=
 Ticket WSDL, commenting out the message, port type, and binding declaratio=
ns as well as replacing the port in the service declaration with the port t=
ype from the Common WSDL - this just left the XSD import statement from the=
 original WSDL.  I tried compiling the Trouble Ticket WSDL again, and the W=
SDL compiler still started eating up 99% of the CPU with no signs of stoppi=
ng.  As a final test, I put the Trouble Ticket WSDL back the way I initiall=
y had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compil=
er didn't even blink while generating all the bindings/stubs/skeletons. =20

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