You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Paul Hanke (JIRA)" <ji...@apache.org> on 2007/07/20 02:43:06 UTC
[jira] Created: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
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, 2.0-RC
Environment: Java 1.5; Windows 2003; VMware Workstation 5.5
Reporter: Paul Hanke
Priority: Minor
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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Paul Hanke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518059 ]
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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Paul Hanke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515740 ]
Paul Hanke commented on CXF-815:
--------------------------------
Another data point to consider: in looking through the Java code generated by the Axis2 WSDL compiler, I noticed some strange looking class names like "TroubleTicketState34" ... this is in addition to another class named "TroubleTicketState" ... the latter maps to a "TroubleTicketState" enumeration in the .xsd, whereas the former maps to a "troubleTicketState" element in the .xsd ... there are a lot of similar artifacts arising from trying to map such upper/lower camel case pairs onto a strictly upper camel case class naming convention.
> 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
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-815:
----------------------------
Fix Version/s: Invalid
> 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
> Fix For: Invalid
>
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514067 ]
Daniel Kulp commented on CXF-815:
---------------------------------
This MAY be the same as CXF-778 which was fixed on trunk a couple days ago. Any chance you could test the latest snapshots (I'm deploying a new one now) or point us to the WSDL's so we can do a quick test?
> 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
> Priority: Minor
>
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin reassigned CXF-815:
-------------------------------
Assignee: jimma
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514107 ]
Bozhong Lin commented on CXF-815:
---------------------------------
If it does not work with latest code in trunk, please ensure to attach the complex schema/wsdl so we can track down the problem.
> 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
> Priority: Minor
>
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518056 ]
jimma commented on CXF-815:
---------------------------
I used WTP to validate this wsdl and schemas and I found there are some invalid schemas are imported or referenced by this wsdl . Below is the details :
1. In /xml/Common-CBETrouble/v1-4/OSSJ-Common-CBETrouble-v1-4.xsd:
Error message : The {type,definition} of element 'troubleTicketStateState' is not validly derived from the {type,definition} of the substitutionHead 'cbetrouble-v1-4:baseTroubleTicketState'
2. In /xml/Common-CBEParty/v1-4/OSSJ-Common-CBEParty-v1-4.xsd
Error message: The {type,definition} of element 'stateState' is not validly derived from the {type,definition} of the substitutionHead 'cbeparty-v1-4:baseState'
3 . In /xml/Common-CBEBi/v1-4/OSSJ-Common-CBEBi-v1-4.xsd
Error message: The {type,definition} of element 'interactionStateState' is not validly derived from the {type,definition} of the substitutionHead 'cbebi-v1-4:baseInteractionState'
When pass these invalid schemas to JAXB, JAXB will be hanging . I will report this issue to JAXB guys.
After I fix these errors by remove the "type" attribute or "substitutionGroup" attribute for these elements and it can generate code for it quickly.
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jimma resolved CXF-815.
-----------------------
Resolution: Fixed
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Paul Hanke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514332 ]
Paul Hanke commented on CXF-815:
--------------------------------
I downloaded the latest 2.0.1 snapshot - same symptom.
> 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
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-815) wsdl2java compiler gets stuck in a loop
on complex XML schemas
Posted by "Paul Hanke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Hanke updated CXF-815:
---------------------------
Attachment: ossj-wsdl.zip
... I've attached the WSDLs/XSDs ... I'll see if I can fit in a test here today (but since I'm a telecommuter out in the boondocks, a snapshot download represents a significant time investment - I'm still on dial-up!) ... btw, which snapshot version should I be looking at (2.0/2.0.1/2.1)?
> 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
> 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 flat XSD. Next, I took the Common API WSDL as a template and started writing 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 compiling 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 declarations as well as replacing the port in the service declaration with the port type 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 WSDL compiler still started eating up 99% of the CPU with no signs of stopping. As a final test, I put the Trouble Ticket WSDL back the way I initially had it and ran it through the Axis2 WSDL compiler - the Axis2 WSDL compiler didn't even blink while generating all the bindings/stubs/skeletons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.