[
https://issues.apache.org/jira/browse/TAP5-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457518#comment-17457518
]
Hudson commented on TAP5-2689:
------------------------------
SUCCESS: Integrated in Jenkins build Tapestry » tapestry-trunk-freestyle #109
(See
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-trunk-freestyle/109/])
Fixing adding_new_columns_to_grid_programattically for TAP5-2689 (thiago: rev
ac5edee3008e581e162b4a673af52742723ef3f8)
* (edit)
tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/AddedGridColumnsDemo.java
> Cached SortedColumnId causing UnknownValueException with Dynamci columns
> ------------------------------------------------------------------------
>
> Key: TAP5-2689
> URL: https://issues.apache.org/jira/browse/TAP5-2689
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Reporter: Benjamin Hartmann
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Major
> Fix For: 5.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Tapestry crashes with an UnknownValueException if a Grid is sorted by a
> column not existing in the PropertyModel of the Grid anymore.
> This can happen if the columns of the grid are dynamic and can change at
> runtime (e.g. using the component paramter "include" and include columns
> based on further conditions).
> A check prior getting the sort constraints of the sort model could prevent
> this issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
