I think it only happens if you use the row instance variable (e.g. "r")
in the "isRendered" attribute e.g.
<a:mycomponent rendered="#{r.isShown}" ... />
So when MyFaces later checks to see if a component was rendered (to save
it's state?) then evaluates the rendered attribute and finds that the
"r" variable has gone out of scope - then it outputs the warning:
8:41:12,979 WARN [VariableResolverImpl] Variable 'r' could not be
resolved.
Thanks,
Kevin
-----Original Message-----
From: Martin Marinschek (JIRA) [mailto:[EMAIL PROTECTED]
Sent: 26 May 2005 07:08
To: Kevin Roast
Subject: [jira] Commented: (MYFACES-246) The WARN level log statement in
VariableResolverImpl.resolveVariable should be DEBUG level
[
http://issues.apache.org/jira/browse/MYFACES-246?page=comments#action_66
323 ]
Martin Marinschek commented on MYFACES-246:
-------------------------------------------
I don't understand your problem well enough, I think. I use dataTable
and the row variables for binding all the time and never have WARN
messages logged out (and I think my log4j is instantiated properly ;)
Can you show the constellation in which the problem occurs?
regards,
Martin
> 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
>
> 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
