Investigate a way to catch and log exceptions without a stack trace to the user

10172
Reporter: omeyn
Assignee: cvizitiu
Type: Improvement
Summary: Investigate a way to catch and log exceptions without a stack trace to the user
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2011-11-08 15:53:18.925
Updated: 2013-08-29 14:45:36.919
Resolved: 2012-11-05 15:14:35.684

Author: mdoering@gbif.org
Created: 2012-11-05 15:03:33.389
Updated: 2012-11-05 15:03:33.389
        
There are 2 kind of exceptions, java and freemarker. Sitemesh parsing fails over the non html freemarker exceptions and we cant catch that unfortunately. We must make sure we dont get any ftl errors.

For java exceptions we can deal with them on various levels, for example we map some already to different portal pages. For the remaining runtime exceptions we could show the main exception name, would that be good?
    

Author: mdoering@gbif.org
Created: 2012-11-05 15:07:37.139
Updated: 2012-11-05 15:07:37.139
        
An example freemarker caused sitemesh error for a non existing or null variable in the ftl:
----------
HTTP ERROR 500

Problem accessing /organization/d44af9a3-e779-40c0-a186-79e7717c6d2b. Reason:

    -1
Caused by:

java.lang.ArrayIndexOutOfBoundsException: -1
	at com.opensymphony.module.sitemesh.html.HTMLProcessor$1.currentBuffer(HTMLProcessor.java:74)