myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Andraschko (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Updated] (MYFACES-1816) Improve tracing view in DebugUtils
Date Mon, 31 Aug 2015 07:42:46 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Andraschko updated MYFACES-1816:
---------------------------------------
    Status: Open  (was: Patch Available)

> Improve tracing view in DebugUtils 
> -----------------------------------
>
>                 Key: MYFACES-1816
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1816
>             Project: MyFaces Core
>          Issue Type: Improvement
>    Affects Versions: 1.1.5
>            Reporter: Michael Heinen
>            Priority: Minor
>         Attachments: DebugUtils.patch
>
>
> I noticed today strange behavior if I change the loglevel for myfaces. Some getters of
backing beans are called although the rendered attribute of a parent component is false. It
is caused by class DebugUtils.traceView.
> I enabled logging via following setting: log4j.logger.org.apache.myfaces=DEBUG
> Sample jsp:
> <t:panelGroup rendered="#{!empty requestScope['myflag']}">
>   <t:dataTable value="#{myController.value}" ...
> </t:panelGroup>
> myController.getValue() is now called if logging is enabled although myflag is not set
in request scope.
> This makes debugging difficult if the app behaves different depending on loglevel settings.
Data can be uninitialized if the parent should not be rendered (or it will be lazy initialized
on each request if BackingBean is request scope and not saved in the request). 
> Therefore I would prefer to skip all components that should not be rendered from output.
> I'll provide a patch as soon as possible (I 'l try this month)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message