You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Julien POLLY (JIRA)" <ji...@apache.org> on 2014/02/13 11:05:19 UTC
[jira] [Updated] (TAP5-2223) New "secure" flag in Select component
has a bug when using option groups
[ https://issues.apache.org/jira/browse/TAP5-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien POLLY updated TAP5-2223:
-------------------------------
Attachment: OptionGroup.zip
The given example contains the relevant code that should reproduce the problem. That is to say :
- an entity with it's value encoder
- a page containing a form with a select using option groups
> New "secure" flag in Select component has a bug when using option groups
> ------------------------------------------------------------------------
>
> Key: TAP5-2223
> URL: https://issues.apache.org/jira/browse/TAP5-2223
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Felix Gonschorek
> Assignee: François Facon
> Priority: Minor
> Attachments: OptionGroup.zip
>
>
> Version 5.4 alpha 25
> Component: Select
> Method: org.apache.tapestry5.corelib.components.Select.findValueInModel
> When checking for exististence of selected value on submit, there is a bug when checking in option groups: the string representation is used to compare with objects ("asSubmitted" should be used but "submittedValue" is used)
> This bug was introduced with: TAP5-2179
> workaround: disable security check for select component.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)