axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1267) WSDL2Java handles duplicate inclusion incorrectly.
Date Fri, 26 Mar 2004 09:39:58 GMT
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Fri, 26 Mar 2004 1:39 AM
       Body:
pls attach your wsdl/xsd's
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1267&page=comments#action_27825

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1267

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1267
    Summary: WSDL2Java handles duplicate inclusion incorrectly.
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             1.1

   Assignee: 
   Reporter: Alex Chen

    Created: Fri, 26 Mar 2004 12:04 AM
    Updated: Fri, 26 Mar 2004 1:39 AM
Environment: Windows XP. JDK 1.4.02

Description:
If duplicate inclusions happens in a schema, the binding classes
create by WSDL2Java are wrong.

For instance, a schema, say, common.xsd which defines an element X
that is used as the return type of a RPC call, is inlcuded in
flow.xsd and config.xsd.  Then master.xsd includes
both flow.xsd and config.xsd. All schema are in the same name space.

When I feed master.xsd to WSDL2Java, it displays a lot of warning
message saying element X has been defined, etc. The generated classes
contain something like XType1.java, or X12.java, etc. instead of
X.java, yet the SOAP port interface class has a method something
like public X getX().

Since no class X is generated, the code fails to compile.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message