I think it only happens if you use the row instance variable (e.g. "r")
in the "isRendered" attribute e.g.
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 o
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
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
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
>
> > Or
> >
> > if(log.isWarnEnabled())
> > {
> > log.warn(...);
> > }
> >
> > Testing the log level before logging should be used for performance reasons.
> >
> > Mathias
> >
> > > -Origina
