Jeanfrancois Arcand wrote:
> Oups. I tested the patch using 1.4 (having the impression Costin was
> working with 1.3). I will revert the patch.
Sorry for that...
Both servletapi-4 and 5 need to be reverted.
I'll try to find an alternative solution. The problem is that debugging some
errors is d
Ops...
Sorry - you're right.
There is a way to make it compatible with both 1.3- and 1.4 - but it would
require changing the interface, so probably need to send feedback to the
jcp...
( adding a Throwable getCause() to the interface would make the stack traces
work again ).
Costin
Glenn Nie
Oups. I tested the patch using 1.4 (having the impression Costin was
working with 1.3). I will revert the patch.
Thanks,
-- Jeanfrancois
Glenn Nielsen wrote:
BTW, this does not build with JDK's < 1.4 and if you use a servlet.jar
built with 1.4 in a JVM <1.4 you get a NoSuchMethodError.
This c
BTW, this does not build with JDK's < 1.4 and if you use a servlet.jar
built with 1.4 in a JVM <1.4 you get a NoSuchMethodError.
This change for jakarta-servletapi-4 need to reverted for now.
Glenn
Costin Manolache wrote:
this is for servetapi_4.
Same applies to servletapi_5 ( I already sent
this is for servetapi_4.
Same applies to servletapi_5 ( I already sent a patch few weeks ago ).
The problem is that JDK1.4 stack traces can't find the root cause.
AFAIK nothing in the servlet or JSP specs requires breaking the normal
contract for exceptions - which is to pass the root cause to t
