Found some time, and upgraded the patch so that it can be applied against SVN trunk.
Having said that, when reviewing the functionality, I think that there's some more code areas (even in Marshaller) where exceptions are logged only (using a log directly) rather than going through the new ErrorHandler. Question: would you be willing to help us here ? Werner Werner Guttmann wrote: > Hi, > > in an ideal world, there should be no need to have to apply patches > manually again and again. > > Having said that, this is an open source project, with a fair number of > committers but less time at hand than at usual times (speaking mainly > for myself here). > > Let me review whether I can find time to have a look at this in the next > few days. > > Werner > > Massimiliano Del Matto wrote: >> Referring to JIRA issue CASTOR-1691, I still can't find any >> (un)marshalling error handler in latest version of Castor XML. >> So I had to patch it by myself adding the interface and classes (and >> modifying the Marshaller class) as described in the above issue to >> have un/marshalling exceptions being thrown. >> My question is: in the project I'm working on we need such an error >> handler _and_ to keep castor-[version]-xml.jar up-to-date within >> latest versions. Will I have to manually patch it every time or this >> issue could be included in future versions? >> >> Thanks, Massimiliano >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
