[
https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991903#comment-14991903
]
Jochen Kemnade commented on TAP5-2490:
--------------------------------------
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)
