axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-...@ws.apache.org
Subject [jira] Updated: (AXIS-1589) SerializationContext.serialize(*,*,*,*,Boolean.FALSE) adds types
Date Tue, 05 Oct 2004 14:38:33 GMT
The following issue has been updated:

    Updater: toby cabot (mailto:toby@caboteria.org)
       Date: Tue, 5 Oct 2004 7:38 AM
    Changes:
             Attachment changed to axis-no-types-patch.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1589?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1589

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1589
    Summary: SerializationContext.serialize(*,*,*,*,Boolean.FALSE) adds types
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             Serialization/Deserialization
   Versions:
             1.2RC1

   Assignee: 
   Reporter: toby cabot

    Created: Tue, 5 Oct 2004 7:37 AM
    Updated: Tue, 5 Oct 2004 7:38 AM
Environment: fedora core 2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
cvs HEAD as of 2004-10-04

Description:
Hi.

I'm working on an application that needs to xml-serialize trees of wsdl2java-generated objects
to an XML document so it can e.g. save them to a file.  I'm using the 1-argument constructor
and the 5-argument SerializationContext.serialize() method but it seems to ignore the Boolean
sendType argument; it adds types to the output whether the value is Boolean.TRUE or Boolean.FALSE.

The problem seems to be that SerializationContext has a flag (sendXSIType) to indicate whether
the types should be sent, but serialize() never sets that variable so when it calls specific
type serializers (e.g. BeanSerializer) and then they call back to StartElement the caller's
argument has been "forgotten" and it adds the type to the output anyway.

So I've added a patch that seems to fix the problem.  It caches the value of sendXSIType,
sets it based on the user's preference, and then sets it back before exiting serialize().
 It seems to pass all-tests and it respects the value of the caller's sendType argument.



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