You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Pierce Wetter (JIRA)" <ji...@apache.org> on 2010/04/01 02:18:27 UTC
[jira] Updated: (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 ]
Pierce Wetter updated TAP5-1093:
--------------------------------
Description:
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.
was:
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".
Instead, it seems like any nested property in t:include should imply a t:add.
Summary: BeanDisplay, Grid: should support nested properties in t:include, t:add (was: BeanDisplay, Grid: t:include should imply t:add )
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.