Bugs item #1073023, was opened at 2004-11-25 08:28 Message generated for change (Settings changed) made by tdiesler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1073023&group_id=22866
Category: JBossSOAP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Alexei Yudichev (sflexus) >Assigned to: Thomas Diesler (tdiesler) Summary: 3.2.5->3.2.7: Axis deserializes nil Base64Binary as byte[0] Initial Comment: I am migrating from JBoss 3.2.5 to 3.2.7RC1. Apart from some Jetty integration issues, I have discovered that if Axis server (jboss-net.sar) tries to deserialize <defaultData xsi:type="xsd:base64Binary" xsi:nil="1"/> I get corresponding bean's field value as byte[0], not as null. Other SOAP types such as xsd:string, do maintain nul values. In JBoss 3.2.5 base64Binary was working well too. Attached is an archive with Axis debug level logs from JBoss 3.2.5 and 3.2.7RC1. In axis.3.2.7RC1.log, line 38 demonstrates that base64Binary comes as nil. Line 756 demonstrates that this value was deserialized as [EMAIL PROTECTED] In axis.3.2.5.log, Base64Deserializer was not ever popped up, because nil value required no deserializer. What version of Axis is in JBoss 3.2.7RC1? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1073023&group_id=22866 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
