On 8/25/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > I'll revisit the work I've already done one of these days and share my > observations.
...but don't let me keep you from working on this! If you have the itch then by all means go ahead and take it on! Hubert > > On 8/25/05, Joe Germuska <[EMAIL PROTECTED]> wrote: > > One small thing we could do is go through everywhere there is a > > SAXException caught and add code to specifically catch a > > SAXParseException and use the several properties of that type to > > provide considerably more information than we do now. > > SAXParseException can tell you exactly the file name (system ID), > > line number and column where a syntax error occurred. This could > > help a lot when debugging config file problems. > > > > Similarly, there are other places where we throw through exceptions > > from underlying Commons libraries where we could strategically catch > > common exceptions which throw people (like a lookup exception for an > > <html:form> tag) and wrap them with contextual information based on > > years of experience. > > > > It's hard, because when you've been doing this for a while, you can > > forget how you learned to decode some of the messages -- but I've > > been helping a few people get up to speed on Struts again recently > > and it has brought some of this to the foreground. > > > > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
