myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Korherr (JIRA)" <>
Subject [jira] Commented: (MYFACES-2676) Include the whole component tree with all real values in the debug page
Date Fri, 07 May 2010 15:00:48 GMT


Jakob Korherr commented on MYFACES-2676:

I thought about this for some time and I think it is not really possible to do that on facelets
side in this particular case, because to store the debugging infos I need the clientId of
the component in the ValueExpression-wrapper. However I cannot store it as a String, because
components inside UIData or UIRepeat have different clientIds in different cases, but only
one ValueExpression. So I would have to store the component instance on the ValueExpression-Wrapper,
which causes problems for the next postback, because the component instance in the ValueExpression
is not valid anymore.

If you have another idea how to solve this, please tell me! For now I will leave it the way
it is. The only thing I have to add is UEL 2.2 support...

Also it is not a real problem here to have myfaces specific code on api, because this specific
code just creates debugging infos in the request scope. If those infos are not available,
then it is no problem, because the DebugPhaseListener will create them (however, without the

> Include the whole component tree with all real values in the debug page
> -----------------------------------------------------------------------
>                 Key: MYFACES-2676
>                 URL:
>             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.

View raw message