[ 
https://issues.apache.org/jira/browse/OFBIZ-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623405#action_12623405
 ] 

Adrian Crum commented on OFBIZ-1843:
------------------------------------

The purpose of this issue is to modify how exceptions are displayed to the end 
user (in the UI I'm assuming). The patch modifies the behavior of ALL 
FreeMarker exceptions, not just the ones involving the UI.

FreeMarker is also used to print reports and import data (via WebTools).

So, let's say you've configured your installation to display little or no 
information when a FreeMarker exception occurs. Then you try to print a report 
or import some data and a FreeMarker exception occurs. With the current patch, 
you have no way of knowing what went wrong (since you turned off the display of 
exceptions). You would have to change the properties settings, clear the cache, 
and try again.

That's why I suggested putting the exception handling properties in the 
context. The screen rendering context would have one set of properties, and 
report generation or XML import services contexts would have a different set of 
properties.

Maybe I'm being too picky. It just seems to me that the current patch might 
cause confusion down the road.


> Suppress stack traces on front end due to errors in ftl files
> -------------------------------------------------------------
>
>                 Key: OFBIZ-1843
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1843
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>            Reporter: Amit Shinde
>            Assignee: Adrian Crum
>            Priority: Minor
>         Attachments: OFBIZ-1843.patch, OFBIZ-1843.patch
>
>
> We need to find a way to gracefully handle stack traces that appear within 
> freemarker on front end due to errors in ftl files. Instead of displaying 
> stack traces to the end user, we should have a simple, configurable way of 
> controlling levels of error messages that should be displayed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to