David Withers wrote: [snip] Hello,
> After investigating some more I've found that although the XStream docs > say "If a new field is added to the class, deserializing an old version > will leave the field uninitialized", this is not the case. String fields > are initialized to null, even if you set a default value for the field. What is happening? Are you saying that new fields are initialized to null? If so, isn't a possible workaround for this to alter the configuration bean so that when you do a getX it checks if x is null and, if so, sets it to a value? > If you add an enum field then an exception is thrown (which is the > problem I'm hitting). What is throwing the exception? > Taverna is using an old version of XStream - 1.2.1 (November 2006). The > docs on the website must refer to the latest version - 1.3.1 (December > 2008), which would explain the discrepancy. Is updating XStream to the > latest version an option, or does Taverna need to use version 1.2.1 for > some reason? Not that I know. Have you tried changing Taverna to use XStream 1.3.1? > David. Alan ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
