You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org> on 2021/12/02 20:08:00 UTC
[jira] [Closed] (TAP5-2689) Cached SortedColumnId causing UnknownValueException with Dynamci columns
[ https://issues.apache.org/jira/browse/TAP5-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago Henrique De Paula Figueiredo closed TAP5-2689.
-----------------------------------------------------
Fix Version/s: 5.8.0
Resolution: Fixed
> 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)