Filed http://issues.apache.org/bugzilla/show_bug.cgi?id=35984
although from previous experience with the Tomcat team I will predict
the future and tell you exactly what is going to happen: Remy will reply
to my report and close it as INVALID. I'm not yet sure what creative
reason he will come up with, but it's been proven to be historically
highly probable :)
Gili
Crash_neo wrote:
I did some more research for bug #1237966 and it turns out
handling this problem isn't so straight-forward. Tomcat's
ClientAbortException makes the classic mistake of defining
getThrowable() without overriding getCause() to return that same
exception.
I hope you also reported this to the Tomcat Developers? Because if it
really is a mistake from their side, you shouldnot try to work around it
with Wicket, but let them fix it. (You can maybe write a patch for
Wicket for the time beaing, at the most).
If, however, they did it on purpose then forget my words and (try to)
fix it by al means. :D
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
