tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimitris Zenios (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2454) Checklist and Palette should support a default encoder like Select
Date Fri, 10 Apr 2015 19:51:12 GMT

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

Dimitris Zenios commented on TAP5-2454:

I think the reason that a defaultValueEncoder is not provided is because all 3 components
have a List<Object> as selected parameter.

The way default provider works is by getting the class type of the value parameter.In the
specified component the class type is always list.

> Checklist and Palette should support a default encoder like Select
> ------------------------------------------------------------------
>                 Key: TAP5-2454
>                 URL: https://issues.apache.org/jira/browse/TAP5-2454
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Chris Poulsen
>            Priority: Minor
> As the three components are so closely related it would make sense to have them work
in the same way.
> Currently one is forced to supply an encoder when converting a select into one of the
multi-select components (palette/checklist) - That is not necessary if the select worked without
an explicit encoder, the other two components should as well.

This message was sent by Atlassian JIRA

View raw message