[ http://jira.jboss.com/jira/browse/JBSEAM-2287?page=all ] koen handekyn updated JBSEAM-2287: ---------------------------------- Description: EL extension to resolve #{bean[field]}" where field is a composite like "property.subProperty" today bean[field] is a means to resolve properties dynamically. it does however not work for nested properties. it's more powerfull and more intuitive imho if one could pass an expression like "address.street" to resolve these dynamically . an example use case is dynamically building list pages like below where the column fields are configurable (and ideally would support projection of a street.address) <c:forEach items="${managedAccounts.searchFields}" var="field" varStatus="status" <rich:column breakBefore="#{count==1 ? true : false}" <h:inputText value="#{managedAccounts.example[field]}" class="headerSearchField" /> </rich:column> </c:forEach> was: EL extension to resolve #{bean[field]}" where field is a composite like "property.subProperty" today bean[field] is means to resolve dynamic proporties. it does howerver not werk for nested properties. it's more powerfull and more intuitive imho if one could pass an expression like "address.street" to resolve these dynamically > EL extension to resolve #{bean[field]}" where field is a composite like "property.subProperty" > ---------------------------------------------------------------------------------------------- > > Key: JBSEAM-2287 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2287 > Project: JBoss Seam > Issue Type: Feature Request > Components: EL > Reporter: koen handekyn > > EL extension to resolve #{bean[field]}" where field is a composite like "property.subProperty" > today bean[field] is a means to resolve properties dynamically. > it does however not work for nested properties. > it's more powerfull and more intuitive imho if one could pass an expression like "address.street" to resolve these dynamically . > an example use case is dynamically building list pages like below where the column fields are configurable (and ideally would support projection of a street.address) > <c:forEach > items="${managedAccounts.searchFields}" > var="field" > varStatus="status" > > <rich:column > breakBefore="#{count==1 ? true : false}" > > <h:inputText > value="#{managedAccounts.example[field]}" > class="headerSearchField" > /> > </rich:column> > </c:forEach> -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-2287?page=comments#action_12389102 ] Norman Richards commented on JBSEAM-2287: ----------------------------------------- Just glancing at this, I don't see any reason this couldn't be done in JBoss EL. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-2287?page=comments#action_12389135 ] Pete Muir commented on JBSEAM-2287: ----------------------------------- com.sun.facelets.el is facelets hooks into EL. What you post should most definitely work with EL - post a patch against one of the examples so we can replicate locally. -- 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