WSDL2Java fails to interpret the wsdl:import definition
-------------------------------------------------------
Key: AXIS2-1447
URL: http://issues.apache.org/jira/browse/AXIS2-1447
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: nightly
Environment: Win2000 with jre1.5.0_02
Reporter: Jerome Magnet
Used nightly (Oct16, 2006) and found an issue with the WSDL2Java tool regarding
use of the wsdl:import definition in WSDL files.
It prevents the generation of the XmlBean Java classes and resources.
Refer to the email with subject "Compilation error with WSDL2Java and XmlBeans"
I attached two sets of WSDL files:
Set#1: one WSDL file (MyService2.wsdl with WSDL2Java invoke script: wsdl2.bat)
with all interface definitions (WSDL/XSD)
This one is working - I did not check in depth the generated Java files. But,
after a quick tour it seems fine.
Set#2: three WSDL files (other ones)
This one is just a simple split of the one in set#1. It is simply a cascading
pattern of wsdl:import with file1 into file2 into file3.
And, it seeems to be enough to brake the generation of all XmlBeans artifacts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
