[
https://issues.apache.org/jira/browse/TAPESTRY-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1471.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.6
@Order was replaced with @OrderBefore and @OrderAfter which reference the other
propertys by case-insensitive name.
In addition, the BeanModel interface was extended with new versions of add()
that allow new properties to be added positioned relative to existing
properties.
A reorder() method was also added to BeanModel.
> Controlling the order of properties within a BeanModel is too complex and
> needs an improved API
> -----------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1471
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1471
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.6
>
>
> The use of a numeric order, to sort the properties within a bean model, is
> very unwieldy, especially when there's a desire to programmatically add new
> properties (often as new columns in a Grid).
> It would be nice if the BeanModel had methods addFirst(), addLast(),
> addBefore() and addAfter() to allow precise positioning of added properties
> within the model, and perhaps a reorder() method to change the overall order
> in a single go.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
