[
https://issues.apache.org/jira/browse/OFBIZ-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515452
]
Si Chen commented on OFBIZ-1169:
--------------------------------
Leon,
Generally this is a great helper and has significantly cut down on the error
messages thrown. However, one problem is that the exception message no longer
tells you the full location of the file. For example, I get this:
2007-07-25 16:26:15,598 (http-0.0.0.0-8433-Processor4) [
Log4JLoggerFactory.java:96 :ERROR]
Expression haha is undefined on line 64, column 31 in viewprofile.ftl.
The problematic instruction:
----------
==> ${haha} [on line 64, column 29 in viewprofile.ftl]
----------
Java backtrace for programmers:
----------
freemarker.core.InvalidReferenceException: Expression haha is undefined on line
64, column 31 in viewprofile.ftl.
But which viewprofile.ftl? It would be helpful if it could say
component://.../viewprofile.ftl
> Eliminate redundant log messages in screen widgets
> --------------------------------------------------
>
> Key: OFBIZ-1169
> URL: https://issues.apache.org/jira/browse/OFBIZ-1169
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Leon Torres
> Assignee: Si Chen
> Fix For: SVN trunk
>
> Attachments: screen-render-exception.patch, screenwidget-log-fix.patch
>
>
> Currently, if you have a typo or minor bug in a bsh or ftl file that is part
> of a screen widget definition, the resulting error message in the log and on
> screen can be overwhelming. This causes a serious usability issue with
> developers and new users.
> I decided to spend some personal time to see what the source of the log
> "explosion" is and how it can be fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
