axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-...@ws.apache.org
Subject [jira] Closed: (AXIS-1488) xs:list itemTypes are forced into namespace {http://www.w3.org/2001/XMLSchema}
Date Thu, 02 Sep 2004 12:20:51 GMT
Message:

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Thu, 2 Sep 2004 5:20 AM

Fixed.

thanks,
dims
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1488

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1488
    Summary: xs:list itemTypes are forced into namespace {http://www.w3.org/2001/XMLSchema}
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             beta-3

   Assignee: 
   Reporter: Steve Green

    Created: Tue, 3 Aug 2004 1:51 PM
    Updated: Thu, 2 Sep 2004 5:20 AM

Description:
Generated code from xs:list items uses the wrong namespace for the list.  Attached is some
wsdl that demonstrates the problem.  newEntryIDs is class ModifyResponseType gets generated
like this:

    org.w3.www._2001.XMLSchema.IDReferenceType[] newEntryIDs;

The reason for this is in SchemaUtils.getListItemType().  The code in question finds the array
type, throws away any namespace prefix, and returns a QName in org.w3.www._2001.XMLSchema.

    return new QName(Constants.URI_2001_SCHEMA_XSD, type + "[]");

Also attached is a patch that partially fixes the problem.  The patch will attempt to find
the QName of the base type for the array.  I call this a partial fix because my patch does
not throw an exception if the list item type cannot be found in the symbol table.  I also
suspect that there might be a better way to solve the problem.


---------------------------------------------------------------------
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