Actually the typo was in the previous version. It should be DESERIALIZE_CURRENT_ELEMENT in both cases in the element deserializer. It is just setting and unsetting the same flag. So the latest patch fixed that. But I'll cross check. /Thomas At 09:11 AM 5/10/2002 -0700, Davanum Srinivas wrote: >Thomas, > >Checked in a slightly modified version of the patch. There was a typo >replacing >"SerializeCurrentElement" with DESERIALIZE_CURRENT_ELEMENT instead of >SERIALIZE_CURRENT_ELEMENT...Please cross-check. > >Thanks, >dims > >--- Tom Jordahl <[EMAIL PROTECTED]> wrote: > > > > Hi Thomas, > > > > Thanks for the patch. How about sending along some documentation for > the new feature? > > Otherwise you will be the only one to know about it! :-) > > > > -- > > Tom Jordahl > > Macromedia > > > > > > -----Original Message----- > > From: Thomas Sandholm [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, May 09, 2002 8:46 PM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: minor patches to xsd:any support > > > > > > Just some minor patches to allow you to turn on and off xsd:any -> object > > deserialization. If it is turned off a dom Element will always be > > constructed. Note the extensibility test case has been updated and has to > > be applied together with the src fixes. > > > > /Thomas > > >===== >Davanum Srinivas - http://xml.apache.org/~dims/ > >__________________________________________________ >Do You Yahoo!? >Yahoo! Shopping - Mother's Day is May 12th! >http://shopping.yahoo.com
Thomas Sandholm <[EMAIL PROTECTED]> The Globus Project(tm) <http://www.globus.org> Ph: 630-252-1682, Fax: 630-252-1997 Argonne National Laboratory
