[richfaces-issues] [JBoss JIRA] Commented: (RF-2923) for attribute in datascroller not handled when using datascroller in custom tags

[Brian Gregory (JIRA)]

    [ http://jira.jboss.com/jira/browse/RF-2923?page=comments#action_12408445 ] 
            
Brian Gregory commented on RF-2923:
-----------------------------------

Comment from Nick Belaevski:

The reason for making "for" EL=false is the phase listener object implemented for RF-1133 that resets model before rendering response. If "for" attribute has dynamic value than it's possible to assign new value during rendering and that will fail to work.
We've discussed the case and decided to make the change, but now it brings problems...

We're working on that. As a workaround you can try to use ${...} instead of #{...} in custom tags. I haven't checked that for now, but maybe it'll help.


> for attribute in datascroller not handled when using datascroller in custom tags
> --------------------------------------------------------------------------------
>
>                 Key: RF-2923
>                 URL: http://jira.jboss.com/jira/browse/RF-2923
>             Project: RichFaces
>          Issue Type: Bug
>    Affects Versions: 3.2.0
>            Reporter: Alan Stewart
>         Assigned To: Nick Belaevski
>             Fix For: 3.2.1
>
>
> Have writtem custom JSF tags that incorporate the rich:datascroller.
> We pass in the id of the rich:dataTable in our custom tag and the datascroller has working using this in versions up until 3.1.4.SR1. Changed to 3.2.0.GA  and now without any other code changes, I get an error:
> could not find dataTable for datascroller j_id171. When we hard-code the id of the dataTable in the "for" attribute of the rich:datascoller, it all works OK.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira