axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Jordahl (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-1589) SerializationContext.serialize(*,*,*,*,Boolean.FALSE) adds types
Date Fri, 12 Nov 2004 14:33:28 GMT
     [ http://nagoya.apache.org/jira/browse/AXIS-1589?page=comments#action_55396 ]
     
Tom Jordahl commented on AXIS-1589:
-----------------------------------

Toby,  I deleted the "extra" patches, but I think I deleted the actual Nov 1 patch that was
the right one (oops).  Can you re-attach your final patch against the current CVS source.
 The one there now is dated October 20, and I don't think it is the right one.

> SerializationContext.serialize(*,*,*,*,Boolean.FALSE) adds types
> ----------------------------------------------------------------
>
>          Key: AXIS-1589
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1589
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: 1.2RC1
>  Environment: fedora core 2
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
> cvs HEAD as of 2004-10-04
>     Reporter: toby cabot
>  Attachments: axis-no-types-patch.txt
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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