I'm the bug-creator and if the usage of system property is unacceptable, then i'll suggest NestableException should be changed to conform better to how JDK 1.4 prints exception - not just to be "complaint", but just to do the most reasonably expected thing...which is: Print the top-most exception first, and print the lowest last.
/max ----- Original Message ----- From: "Henri Yandell" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Thursday, January 16, 2003 9:16 PM Subject: [lang] Bug #14357 > I'd like to get this bug/issue dealt with. > > http://issues.apache.org/bugzilla/show_bug.cgi?id=14357 > > NestableException [in Beta 1 apparantly] prints the stack trace with the > most relevant error at the bottom and not the top, as is common in most > app's. > > Does anyone know if this was fixed and the bug not closed, or if it's > still an issue? > > The bug-creator's suggestion is a system property. Obviously this has > serious issues and probably isn't acceptable. How else can it be solved? > > Hen > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
