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/10/23 10:41:27 UTC

[jira] [Updated] (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:all-tabpanel ]

Jochen Kemnade updated TAP5-2490:
---------------------------------
    Attachment: 0001-TAP5-2490-use-UrlEventContext-instead-of-ArrayEventC.patch

I think I' able to reproduce the issue now. I've tried the approach you suggested (using an aggregated event context) but haven't succeeded so far. The patch shows what I've tried so far.

> 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)