[
https://issues.apache.org/jira/browse/MYFACES-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865223#action_12865223
]
Leonardo Uribe commented on MYFACES-2676:
-----------------------------------------
I prefer have the debug info extracted on DebugPhaseListener without callstack.
Debugging code should be on debugging classes. One design criteria is keep
things simple. The idea of have better debugging information is very good, but
the cost involved in this specific detail is too high for me. Have a call to
FacesContext.getCurrentInstance().isProjectStage on getValueExpression() and
setValue(), a code that is called many, many times on jsf lifecycle does not
look good for performance.
> Include the whole component tree with all real values in the debug page
> -----------------------------------------------------------------------
>
> Key: MYFACES-2676
> URL: https://issues.apache.org/jira/browse/MYFACES-2676
> Project: MyFaces Core
> Issue Type: New Feature
> Components: JSR-314
> Affects Versions: 2.0.0
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
>
> now that we have the tree-visiting in place, we can do both:
> - first write out the component-tree master, with only expressions in place
> (see MYFACES-2667)
> - second we write out the tree how it is really evaluated by the components,
> with the real component values
> the more debugging information, the better!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
