+1
Ideally, the UIComponent#isRendered() should cache the value on a per-phase
and per-iteration basis. It would be awesome too if iteration components
implement a common interface or abstract class, which should also simplify
a lot of other things related to a.o. setting the currently iterated item
and state saving.
Cheers, B
On Fri, Jan 9, 2015 at 7:00 PM, manfred riem <manfred.riem_at_oracle.com>
wrote:
> Whoops, sending to right list. Please ignore it on the other.
>
> -------- Original Message -------- Subject: [jsr344-experts]
> [941-ReduceELCalls] DISCUSSION Date: Fri, 09 Jan 2015 11:51:14 -0600 From:
> manfred riem <manfred.riem_at_oracle.com> <manfred.riem_at_oracle.com> Reply-To:
> jsr344-experts_at_javaserverfaces-spec-public.java.net Organization: Oracle
> Corporation To: jsr344-experts_at_javaserverfaces-spec-public.java.net CC: Max
> Starets <max.starets_at_oracle.com> <max.starets_at_oracle.com>, Andy Schwartz
> <andy.schwartz_at_oracle.com> <andy.schwartz_at_oracle.com>
>
> Hi all,
>
> As we all know the number of times an EL expression is evaluated during
> render is higher than it could be.
>
> To see if there is a potential to reduce that number I want to ask the
> most important question first as it determines whether or not this issue is
> even worth pursuing?
>
> *Is it safe to assume that during rendering and not as a child of an
> iterating component the value of the EL expression will stay stable?*
>
> Regards,
> Manfred
>
>