You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Marinschek (JIRA)" <my...@incubator.apache.org> on 2005/05/26 11:36:53 UTC
[jira] Closed: (MYFACES-246) The WARN level log statement in VariableResolverImpl.resolveVariable should be DEBUG level
[ http://issues.apache.org/jira/browse/MYFACES-246?page=all ]
Martin Marinschek closed MYFACES-246:
-------------------------------------
Resolution: Fixed
Fix Version: Nightly Build
I'll commit it as soon as committing works again ;)
> The WARN level log statement in VariableResolverImpl.resolveVariable should be DEBUG level
> ------------------------------------------------------------------------------------------
>
> Key: MYFACES-246
> URL: http://issues.apache.org/jira/browse/MYFACES-246
> Project: MyFaces
> Type: Improvement
> Versions: 1.0.9 beta
> Environment: WinXP, Pentium4, TomCat 5, MyFaces 1.0.9
> Reporter: Kevin Roast
> Assignee: Martin Marinschek
> Priority: Minor
> Fix For: Nightly Build
>
> The WARN level log statement in VariableResolverImpl.resolveVariable should be DEBUG level.
> The reason for this is that if you use DataTable or any other custom component that uses temporary variables for binding (e.g. Row variables in a datatable) then the variables resolver will spit out WARN level statements like this:
> WARN [VariableResolverImpl] Variable 'r' could not be resolved.
> Because the variable is no longer in Scope it cannot be resolved - this fine, but the WARN level is probably too high, it could cause a minor performance issue in large apps as the WARN output String is always constructed with an If statement surrounding it to check the log level.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira