You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Volker Weber (JIRA)" <de...@myfaces.apache.org> on 2007/01/31 10:55:06 UTC
[jira] Resolved: (TOBAGO-262) descendants of button with
immediate=true can't be immediate=false
[ https://issues.apache.org/jira/browse/TOBAGO-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Volker Weber resolved TOBAGO-262.
---------------------------------
Resolution: Fixed
> descendants of button with immediate=true can't be immediate=false
> ------------------------------------------------------------------
>
> Key: TOBAGO-262
> URL: https://issues.apache.org/jira/browse/TOBAGO-262
> Project: MyFaces Tobago
> Issue Type: Bug
> Components: Core
> Reporter: Volker Weber
> Assigned To: Volker Weber
> Fix For: 1.0.10
>
>
> following situation:
> a button with immediate=true, a popup-facet on this button.
> inside this popup a button with no immediate, (or immediate=false).
> the action of the button inside the popup is execuded in applyRequestValue phase instead of in invokeApplication.
> due to the implementation of queueEvent() in jsf api (tested with myfaces and RI) immediate of UICommand components
> are passed to all descendants
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.