You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Udo Schnurpfeil (JIRA)" <de...@myfaces.apache.org> on 2013/08/30 16:29:52 UTC
[jira] [Commented] (TOBAGO-1301) tx:selectOneChoice not submitted
after switching from readonly to !readonly
[ https://issues.apache.org/jira/browse/TOBAGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754723#comment-13754723 ]
Udo Schnurpfeil commented on TOBAGO-1301:
-----------------------------------------
A question: Did you manipulate the readonly=false to readonly=true on the client site manuelly?
If yes: This doesn't work and should not work, because the server side model of the readonly state is false and must not manipulate by client requests directly.
This is for security reasons.
Otherwise a user or script on the client site may override protections of the application that are e.g. role depending.
> tx:selectOneChoice not submitted after switching from readonly to !readonly
> ---------------------------------------------------------------------------
>
> Key: TOBAGO-1301
> URL: https://issues.apache.org/jira/browse/TOBAGO-1301
> Project: MyFaces Tobago
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-alpha-2
> Reporter: Michael Bädorf
> Attachments: TOBAGO-1301.patch
>
>
> A <tx:selectOneChoice> defined as readonly initializing a page. Due to user actions the listbox should be switched to readonly = false. The element is rendered correctly but its value won't be submitted.
> I had to mention that switching from readonly to readonly false happsens in an ajax call
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira