You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/03/23 02:00:58 UTC

[jira] Updated: (AXIS-1258) xsd:list of QName is not handled properly

The following issue has been updated:

    Updater: gawor (mailto:gawor@mcs.anl.gov)
       Date: Mon, 22 Mar 2004 5:00 PM
    Comment:
A patch for the xsd:list QName serialization/deserialization problem   
    Changes:
             Attachment changed to listqname.path
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1258&page=history

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1258
    Summary: xsd:list of QName is not handled properly
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             Serialization/Deserialization

   Assignee: 
   Reporter: gawor

    Created: Mon, 22 Mar 2004 4:58 PM
    Updated: Mon, 22 Mar 2004 5:00 PM

Description:
This is resubmission from bugzilla (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27356):

The following definition:

       <xsd:element name="foo">
          <xsd:simpleType>
            <xsd:list itemType="xsd:QName" />
          </xsd:simpleType>
       </xsd:element>

With values such as xmlns:n1=foo xmlns:n2=foo2 n1:bar n2:bar2 is serialized as:

<foo>{foo}bar {foo2}bar2</foo>

Which is not correct. Also even if serialized properly the deserialization is 
invalid. The SimpleListDeserializer tries to pass the token value of QName
(String) constructor but this is wrong since the QName(String) constructor only 
accepts a localName and also proper namespace prefix resolution is not 
performed.

The attached patch fixes the serialization and deserialization problems.




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