You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Kočí (Created JIRA)" <de...@myfaces.apache.org> on 2011/12/12 20:29:30 UTC
[jira] [Created] (MYFACES-3419) AjaxBehavior.isImmediateSet():
information allows an associated client behavior renderer to fall back on
the parent component's immediate status
AjaxBehavior.isImmediateSet(): information allows an associated client behavior renderer to fall back on the parent component's immediate status
------------------------------------------------------------------------------------------------------------------------------------------------
Key: MYFACES-3419
URL: https://issues.apache.org/jira/browse/MYFACES-3419
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.11, 2.0.5
Environment: myfaces trunk
Reporter: Martin Kočí
Assignee: Martin Kočí
Priority: Minor
1) JavaDoc AjaxBehavior.isImmediateSet():
Tests whether the immediate attribute is specified. Returns true if the immediate attribute is specified, either as a locally set property or as a value expression. This information allows an associated client behavior renderer to fall back on the parent component's immediate status when immediate is not explicitly specified on the AjaxBehavior.
myfaces don't implement this feature in HtmlAjaxBehaviorRenderer
2) isComponentImmediate use introspection for evaluation of isImmediate - that is unefficient (Contains code comment: Currently implemented by ActionSource and EditableValueHolder but we cannot be sure about both interfaces so lets make introspection calls here - but what means "we cannot be sure about both interfaces" ?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MYFACES-3419) AjaxBehavior.isImmediateSet():
information allows an associated client behavior renderer to fall back on
the parent component's immediate status
Posted by "Leonardo Uribe (Updated) (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe updated MYFACES-3419:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.7
2.0.13
Status: Resolved (was: Patch Available)
I just fix isImmediateSet() logic to check for the value stored on map or if a ValueExpression is set. Thanks to Martin Koci for provide this patch.
> AjaxBehavior.isImmediateSet(): information allows an associated client behavior renderer to fall back on the parent component's immediate status
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-3419
> URL: https://issues.apache.org/jira/browse/MYFACES-3419
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.5, 2.0.11
> Environment: myfaces trunk
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Fix For: 2.0.13, 2.1.7
>
> Attachments: MYFACES-3419.patch
>
>
> 1) JavaDoc AjaxBehavior.isImmediateSet():
> Tests whether the immediate attribute is specified. Returns true if the immediate attribute is specified, either as a locally set property or as a value expression. This information allows an associated client behavior renderer to fall back on the parent component's immediate status when immediate is not explicitly specified on the AjaxBehavior.
> myfaces don't implement this feature in HtmlAjaxBehaviorRenderer
> 2) isComponentImmediate use introspection for evaluation of isImmediate - that is unefficient (Contains code comment: Currently implemented by ActionSource and EditableValueHolder but we cannot be sure about both interfaces so lets make introspection calls here - but what means "we cannot be sure about both interfaces" ?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MYFACES-3419) AjaxBehavior.isImmediateSet():
information allows an associated client behavior renderer to fall back on
the parent component's immediate status
Posted by "Martin Kočí (Updated JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Kočí updated MYFACES-3419:
---------------------------------
Status: Patch Available (was: Open)
> AjaxBehavior.isImmediateSet(): information allows an associated client behavior renderer to fall back on the parent component's immediate status
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-3419
> URL: https://issues.apache.org/jira/browse/MYFACES-3419
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.5, 2.0.11
> Environment: myfaces trunk
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Attachments: MYFACES-3419.patch
>
>
> 1) JavaDoc AjaxBehavior.isImmediateSet():
> Tests whether the immediate attribute is specified. Returns true if the immediate attribute is specified, either as a locally set property or as a value expression. This information allows an associated client behavior renderer to fall back on the parent component's immediate status when immediate is not explicitly specified on the AjaxBehavior.
> myfaces don't implement this feature in HtmlAjaxBehaviorRenderer
> 2) isComponentImmediate use introspection for evaluation of isImmediate - that is unefficient (Contains code comment: Currently implemented by ActionSource and EditableValueHolder but we cannot be sure about both interfaces so lets make introspection calls here - but what means "we cannot be sure about both interfaces" ?)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira