> Well what do propose? I have no problems viewing the stack trace
> therefore I think it's fine: if you want more logging why not add an
> aspect, I really don't see why that should be such a pain?
I understand that it's not directly an Andromda issue. But
addressing Andromda is the easiest way to fix my problem. I simply
added the following lines to the exception template:
public void printStackTrace(java.io.PrintStream ps) {
if (this.getCause() == null) {
super.printStackTrace(ps);
}
else {
this.getCause().printStackTrace(ps);
}
}
public void printStackTrace(java.io.PrintWriter ps) {
if (this.getCause() == null) {
super.printStackTrace(ps);
}
else {
this.getCause().printStackTrace(ps);
}
}
Not very elegant, but that does it right now. Maybe some other
tomcat users will complain in the future and then we can think
about it again.
I also had a quick look at the Throwable source and found some
code that should print stacktraces about a cause-throwable, but
I don't know why this doesn't happen and I decided not to dig into
it any deeper.
Chris
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user
