[jira] Resolved: (MYFACES-2702) Implement composite:clientBehavior

["Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/MYFACES-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved MYFACES-2702.
-------------------------------------

    Fix Version/s: 2.0.1-SNAPSHOT
       Resolution: Fixed

> Implement composite:clientBehavior
> ----------------------------------
>
>                 Key: MYFACES-2702
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2702
>             Project: MyFaces Core
>          Issue Type: Task
>          Components: JSR-314
>    Affects Versions: 2.0.0
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>            Priority: Critical
>             Fix For: 2.0.1-SNAPSHOT
>
>
> Finally we have the documentation and one example that describes how this undocumented tag works. (Thanks to David Geary and Alexander Smirnov)
> The tag attributes are this:
> 1) "event", type String. this is the name of target component event for
> which behavior object will be attached.
> 2) "name", type String - the name of composite component behavior.
> 3) "default", type boolean, defines default composite component event,
> same as the "action" is default for commandLink. There should be only
> one default behavior per composite, exception will be thrown.
> 4) "targets" - the same as for all other <composite:... > tags.
> I'm doing a full review of Behavior api before implement this one, and it seems this tag requires some workarounds to be done on vdl.retargetAttachedObjects. Instead using "for" as target, this one use a combination of "event" and "name", so at first view we need to try what happen when nested composite components are used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.