[
https://issues.apache.org/jira/browse/OFBIZ-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541652
]
David E. Jones commented on OFBIZ-1318:
---------------------------------------
Do we really want to configure this through web.xml?
What about when a screen or form or whatever is rendered in a non-web context
and there is no web.xml?
In the past this happened when passing in a special parameter, so it just had
to be in the parameters Map for the screen, but admittedly that may not be the
best choice.
How about a property in debug.properties, like piggy-backing on verbose or
info? Info is usually on during development only, or when debugging production
servers, and that might be a good option.
Other ideas?
> screen widget show where code came from in html
> -----------------------------------------------
>
> Key: OFBIZ-1318
> URL: https://issues.apache.org/jira/browse/OFBIZ-1318
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Reporter: Si Chen
> Assignee: Jacques Le Roux
> Attachments: widget_boundary_comments.patch,
> widget_boundary_comments.patch, widget_boundary_comments.patch,
> widget_boundary_comments.patch, widget_boundary_comments.patch
>
>
> This should help debugging a lot:
> The screen widget render could put in an HTML comment in the html document if
> log INFO is turned on (or VERBOSE if you really don't like it) to show where
> the text came from. For example, if the screen widget called a form, it
> could put into HTML:
> <!-- Begin XXXX.Forms.xml#FormA -->
> <!-- End XXXX.Forms.xml#FormA -->
> Similarly, if html-template is called it could put into HTML:
> <!-- Begin applications/XXX/x.ftl -->
> <!-- End applications/XXX/x.ftl -->
> etc. etc.
> I think this would be a good debugging tool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
