Newbies can easily do bad code that throws exceptions but those are simply ignored on the server-side logs (System streams). We should print stack traces by default to System.err too, users may override this behaviour if required.

svn changeset:3729/svn branch:trunk

1 files changed, 4 insertions, 1 deletions

diff --git a/src/com/itmill/toolkit/Application.java b/src/com/itmill/toolkit/Application.java
index b9ba29e7e4..2dbca6560e 100644
--- a/src/com/itmill/toolkit/Application.java
+++ b/src/com/itmill/toolkit/Application.java
@@ -1017,7 +1017,8 @@ public abstract class Application implements URIHandler, Terminal.ErrorListener
      * Invoked by the terminal on any exception that occurs in application and
      * is thrown by the <code>setVariable</code> to the terminal. The default
      * implementation sets the exceptions as <code>ComponentErrors</code> to
-     * the component that initiated the exception.
+     * the component that initiated the exception and prints stack trace to
+     * System.err.
      * </p>
      * <p>
      * You can safely override this method in your application in order to
@@ -1029,6 +1030,8 @@ public abstract class Application implements URIHandler, Terminal.ErrorListener
      * @see com.itmill.toolkit.terminal.Terminal.ErrorListener#terminalError(com.itmill.toolkit.terminal.Terminal.ErrorEvent)
      */
     public void terminalError(Terminal.ErrorEvent event) {
+        // throw it to System.err too
+        event.getThrowable().printStackTrace();
 
         // Finds the original source of the error/exception
         Object owner = null;