Israel, Israel, Kirk wrote: > > > >>org.exolab.castor.xml.naming=mixed >>as by default is is commented. As to why and when this has been > > changed, no idea .. ;-). > > There's a non-zero chance that we've been using a "hacked" jar with a > custom castor.properties (rather than just having a local > castor.properties on the classpath to override...though I think that > should be our preferred method.) > > > > >>>* for that matter, at some point did the default preference change >>>from nested types to attributes for Strings and other simple-ish >>>types? (I noticed that when I write an object now) I think this one I > > >>>could change in the properties. >> >>Looks like >> >>#org.exolab.castor.xml.introspector.primitive.nodetype=element >> >>could be your friend .. ;-). > > > Heheh, not to mention > > org.exolab.castor.indent=true > > :-) > > Thanks! Although clearly the fault was somewhat mine for not > researching castor.properties, I do have to say that > "java.lang.NullPointerException" is pretty ugly jargon for a "Can't > reconcile this xml with the class I'm trying to make from it" -- should > I put in a feature request for a more useful error message in this kind > of case? Feel free to do so at http://jira.codehaus.org/browse/CASTOR.
(Actually, I almost wish "debug" wasn't just boolean, but with > off, on, and "errors only" modes...) > > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
