TC 3.2 - Better logging messages when something bad happens?

[David Rees]

While doing some development, I started getting this Exception:

org.apache.jasper.JasperException: error in invoking method
        at
org.apache.jasper.runtime.JspRuntimeLibrary.createTypedArray(JspRuntimeLibra
ry.java:353)
        at
org.apache.jasper.runtime.JspRuntimeLibrary.introspecthelper(JspRuntimeLibra
ry.java:194)

I was trying to populate a bean with an array from a form, but the bean was
throwing an exception during the population.  The confusing part was that
there was nothing in any logs to help me figure out what was going on
because the JspRuntimeLibrary was catching the exception and suppressing the
real error message.

Simply printing out a stack trace like this helped me find the problem in no
time (diff against TC 3.2.1 release):

--- ./src/share/org/apache/jasper/runtime/JspRuntimeLibrary.java.orig   Tue
Dec 19 20:51:23 2000
+++ ./src/share/org/apache/jasper/runtime/JspRuntimeLibrary.java        Tue
Dec 19 20:38:50 2000
@@ -349,6 +349,7 @@
                method.invoke (bean, new Object[] {tmpval});
            }
        } catch (Exception ex) {
+           ex.printStackTrace();
            throw new JasperException ("error in invoking method");
        }


Is there any reason to not include a similar patch in the official tree?

-Dave