You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/11/05 18:10:28 UTC

[jira] [Comment Edited] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

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

Jochen Kemnade edited comment on TAP5-2490 at 11/5/15 5:09 PM:
---------------------------------------------------------------

For Select, this turns out to be much more complicated than expected depending on the types of the context values and whether the {{encoder}} parameter is bound or not. What if the {{value}} and the {{context}} have the same type, a global value encoder is registered for that type and a different value encoder is passed via the {{encoder}} parameter? Even then, the global encoder should be used if I'm not mistaken, so my last commit is was probably not the correct way to fix this. I'll have another look tomorrow.


was (Author: jkemnade):
For Select, this turns out to be much more complicated than expected depending on the types of the context values and whether the {{encoder}} parameter is bound or not. What if the {{encoder}} and the {{encoder}} have the same type, a global value encoder is registered for the type and a different value encoder is passed via the {{encoder}} parameter? Even then, the global encoder should be used if I'm not mistaken, so my last commit is was probably not the correct way to fix this. I'll have another look tomorrow.

> Autocomplete and Select context values does not work when context has to pass through a value encoder
> -----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2490
>                 URL: https://issues.apache.org/jira/browse/TAP5-2490
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Dimitris Zenios
>         Attachments: 0001-TAP5-2490-use-UrlEventContext-instead-of-ArrayEventC.patch
>
>
> Context passed down to select and autocomplete should be send as is (UrlEventContext) to parent container instead of coercing it to List<String> context first



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)