[jira] [Commented] (TAP5-2223) New "secure" flag in Select component has a bug when using option groups

2014-02-15 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on TAP5-2223:
---

Commit a4fe5cedcd06ac5f438d04d9e3daaae1164a2381 in tapestry-5's branch 
refs/heads/master from ffacon
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=a4fe5ce ]

TAP5-2223 : New "secure" flag in Select component has a bug when 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)

[jira] [Commented] (TAP5-2223) New "secure" flag in Select component has a bug when using option groups

2014-02-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on TAP5-2223:
---

Commit 32e8e2f626f9da1d64e13bbd7e572a33dd9cab22 in branch refs/heads/master 
from ffacon
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=32e8e2f ]

TAP5-2223 : New "secure" flag in Select component has a bug when 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)

[jira] [Commented] (TAP5-2223) New "secure" flag in Select component has a bug when using option groups

2014-02-13 Thread JIRA 

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

François Facon commented on TAP5-2223:
--

Thank you julien.
Your example will help me to provide a test case. 

Regards
François

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