Thanks for the quick feedback! I've opened a JIRA issue, as suggested:
https://issues.apache.org/jira/browse/NET-374 Take care, Daniel -----Original Message----- From: sebb [mailto:[email protected]] Sent: Tuesday, March 15, 2011 7:50 PM To: Commons Users List Subject: Re: [NET] ParserInitializationException root cause On 15 March 2011 23:40, Daniel Gredler <[email protected]> wrote: > Hi all, > > > > I have a question about ParserInitializationException; it appears to > have its own "rootCause" instance variable, rather than using > RuntimeException's constructors which allow a cause to be specified > (ParserInitializationException extends RuntimeException). So for example > on line 53 of the class [1], I would expect to see a simple invocation > to "super(message, rootCause)". > > > > The reason this has come up is that we're logging these exceptions using > log4j, but because ParserInitializationException doesn't use the > standard JDK exception chaining, we don't get visibility into the root > issue. Does anyone know why this exception was built this way? Commons NET 1.4.1 targets Java 1.3+, and RuntimeException only added chaining in 1.4. Commons NET 2.x targets 1.5+, but was derived from the 1.x codeline. > Would anyone else consider this a bug? Feel free to raise JIRA issue to get this changed. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
