You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/12/02 20:04:00 UTC

[jira] [Commented] (TAP5-2689) Cached SortedColumnId causing UnknownValueException with Dynamci columns

    [ https://issues.apache.org/jira/browse/TAP5-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452585#comment-17452585 ] 

ASF subversion and git services commented on TAP5-2689:
-------------------------------------------------------

Commit fda8de0ea4dbe40a2999242be32d57f1217a9a39 in tapestry-5's branch refs/heads/master from Benjamin Hartmann
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=fda8de0 ]

TAP5-2689 preventing unknown value exception with sorted grid in case of cached sorted column is not part of property model anymore.


> 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
>            Priority: Major
>          Time Spent: 10m
>  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)