You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org> on 2011/10/18 02:15:10 UTC

[jira] [Closed] (TAP5-1093) BeanDisplay, Grid: should support nested properties in t:include, t:add

     [ https://issues.apache.org/jira/browse/TAP5-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1093.
--------------------------------------

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship
    
> BeanDisplay, Grid: should support nested properties in t:include, t:add 
> ------------------------------------------------------------------------
>
>                 Key: TAP5-1093
>                 URL: https://issues.apache.org/jira/browse/TAP5-1093
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Pierce Wetter
>            Assignee: Howard M. Lewis Ship
>
> Say you have something one object removed you want to display like "user.firstName". 
> If you try to blindly add this to a grid using t:include, you get an error because its "not part of the bean model" because despite the documentation stating that it "understands property expressions", it doesn't!
> Similarly, t:add="user.login" doesn't work either, because that adds an empty property!
> Unfortunately, this will be a challenge to fix without breaking all existing uses of t:add! 
> Suggestion: If t:include or t:add sees prop:user.login, it should then interpret that as a nested property expression, and create the appropriate property conduit. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira