[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-124) Comparing of null values hardcoded in ShuttleSortableTableModel

[Keith D. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/spring/browse/RCP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Donald updated RCP-124:
-----------------------------

    Assignee:     (was: Keith Donald)

> Comparing of null values hardcoded in ShuttleSortableTableModel
> ---------------------------------------------------------------
>
>                 Key: RCP-124
>                 URL: http://opensource.atlassian.com/projects/spring/browse/RCP-124
>             Project: Spring Framework Rich Client Project
>          Issue Type: Bug
>            Reporter: Adrian Gygax
>            Priority: Minor
>         Attachments: ShuttleSortableTableModel_nullvalue.patch
>
>
> org.springframework.richclient.table.ShuttleSortableTableModel has hardcoded behaviour for comparing null values. This makes it impossible for Comparators to handle them. As the Java API docs only recommend Comparables (and not Comparators) to throw a NullPointerException if compared to nulls, the hardcoded behaviour should only be executed if no Comparators are specified.
> For example, in my application I need Dates to be sorted in a non-default way. A null value should be larger instead of smaller than anything. This can easily implemented with a Comparator, if ShuttleSortableTableModel lets it treat this case.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira