Can someone add this to the issue tracker?
___
Kito D. Mann | @kito99 | Author, JSF in Action
Virtua, Inc. |
http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com | @jsfcentral
+1 203-998-0403
* Listen to the Enterprise Java Newscast: *http://
<
http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com
<
http://ww.enterprisejavanews.com>*
* JSFCentral Interviews Podcast:
http://www.jsfcentral.com/resources/jsfcentralpodcasts/
* Sign up for the JSFCentral Newsletter:
http://oi.vresp.com/?fid=ac048d0e17
On Fri, May 22, 2015 at 4:01 AM, Cagatay Civici <cagatay.civici_at_gmail.com>
wrote:
> I also raised it some time ago but never got too much attention.
>
> As a component library developer, we have a couple of behaviors as well
> and state saving is a pain with them.
>
> Regards,
>
> Cagatay Civici
> PrimeFaces Lead
> PrimeTek Informatics
> www.primefaces.org
>
> On Friday 22 May 2015 at 10:55, arjan tijms wrote:
>
> Hi,
>
> Interesting point, certainly something we should at least take a closer
> look at.
>
> Kind regards,
> Arjan
>
> On Friday, May 22, 2015, Rudy De Busscher <rdebusscher_at_gmail.com> wrote:
>
> Hi Experts,
>
> Recently I came across the fact that the Behaviour API is not using the
> StateHolder.
>
> This means that EL Expressions in attributes of custom ClientBehaviours
> are executed during the buildView step and not during the 'rendering'
> (getScript() ) of the clientBehaviour.
>
> As a consequence, the EL can't reference a var defined in the dataTable.
>
> Any plans / ideas for adding this in some next version?
>
> Thanks for the feedback
> Rudy.
>
>
>
>