[ http://issues.apache.org/jira/browse/MYFACES-27?page=comments#action_66811 ] Oliver Rossmueller commented on MYFACES-27: -------------------------------------------
One point upfront: JSCookMenu is completely broken in the current trunk, any menu click ends in an 404 error page (at least in the examples webapp). But now to the original issue: immediate=true is only one part of the problem, it can be changed to false (by default or by configuration attribute) without problems, but this won't solve the issue. To store values the corresponding form has to be submitted, too. This would require some modifications in the JSCookMenu javascript function named cmItemMouseUp. Instead of opening the target link in a (new) browser window it would be necessary to submit the form which holds the values to be stored. So there are some points to discuss: * do we want to fork JSCookMenu for the purpose of resolving this issue * how is the form id handed over to the menu * should it be possible to submit different forms so we would have to configure the form id on menu item level > JSCookmenu cannot be used for storing data > ------------------------------------------ > > Key: MYFACES-27 > URL: http://issues.apache.org/jira/browse/MYFACES-27 > Project: MyFaces > Type: Bug > Versions: 1.0.7 beta > Environment: JBoss 4.0 > Reporter: > > JSCookmenu has hardcoded "immediate" attribute on "true". This cause that an > action, which should store data from the view, is executed after the > apply_request_values-phase instead of the application-execute-phase. But at > that time the model values are not updated with the view-values, so a empty > objekt is stored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
