>
> > Or
> >
> > if(log.isWarnEnabled())
> > {
> > log.warn(...);
> > }
> >
> > Testing the log level before logging should be used for performance reasons.
> >
> > Mathias
> >
> > > -Origina
should be used for performance reasons.
>
> Mathias
>
> > -Original Message-
> > From: Martin Marinschek [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, May 26, 2005 10:54 AM
> > To: MyFaces Development
> > Subject: Re: [jira] Commented: (MYFACES-246) The WARN
To: MyFaces Development
> Subject: Re: [jira] Commented: (MYFACES-246) The WARN level
> log statement in VariableResolverImpl.resolveVariable should
> be DEBUG level
>
>
> Hmmm...
>
> I would say that attributes of components should only be evaluated in
> the contex
Hmmm...
I would say that attributes of components should only be evaluated in
the context in which they exist - that would mean that the call to the
isRendered attribute is wrong in this case, if it is not executed
while a datatable iteration is happening.
What would you say?
regards,
Martin
O
[
http://issues.apache.org/jira/browse/MYFACES-246?page=comments#action_66323 ]
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
ble 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
