> > The second set of patches is for reformatting of the exception > printing. Dealing with it for a while, I just couldn't handle the way > they were printed anymore so I changed it around a bit. I realize > this is mainly a personal preference, but I thought I'd send it out > for feedback. Outline of changes made: > > -Flipped the order NestedExceptions are printed in to be current > exception first then sub-exception, and added a "Root Cause:" line > above the sub-exception. This way, when a user is reading the log > from bottom to top, they see the sub-exception first (probably where > the real problem is) and it's seperated from the above exception to > provide a visual break. > > -Changed NestedThrowable.Util.getMessage() to not use "nested" in > constructing the message. It seemed to be only redundant info that > was always printed out later on. This change does scare me a bit in > that I'm not sure what other code paths rely on info being included by > "nested". Any thoughts? > > >
Please show examples for what the exception output will look like... Looks like your patch to NestedThrowable only losses information... but it is hard to tell. Show me a before and after and why you think after is better please =) --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
