Composite Components
Tag clientBehavior


Declares that the composite component whose contract is declared by the <composite:interface> in which this element is nested exposes an implementation of ClientBehaviorHolder suitable for use as the target of attached objects in the using page. Any attached objects suitable for implementations of ClientBehaviorHolder may be attached to the composite component.



Tag Information
Tag ClassNone
TagExtraInfo ClassNone
Body ContentJSP
Display NameNone

Attributes
NameRequiredRequest-timeTypeDescription
eventfalsefalsejavax.el.ValueExpression
(must evaluate to java.lang.String)

The evaluated value of this attribute will be passed as the first argument to the addClientBehavior() method on ClientBehaviorHolder.

defaultfalsefalsejavax.el.ValueExpression
(must evaluate to boolean)
If the evaluated value of this attribute is true, the page author may omit the the "event" attribute when specifying the behavior in the using page. This is analogous to "action" being the default event for commandLink. The usage of this attribute assumes only one clientBehavior is declared in this composite component. If more than one is specified, only the first one is used in the case of a using page with no event attribute.
nametruefalsejavax.el.ValueExpression
(must evaluate to java.lang.String)

The value of this attribute maps back to the "for" attribute on an attachable object nested within a composite component. If the "targets" attribute is not specified, this value also represents the component ID of the target component within the that the <composite:implementation> ActionListener should be mapped to.

targetsfalsefalsejavax.el.ValueExpression
(must evaluate to java.lang.String)

If present, this must be a space (not tab) separated list of client ids (relative to the top level component) of components within the <composite:implementation> section. Space is used as the delimiter for compatibility with the IDREFS and NMTOKENS data types from the XML Schema.


Variables
No Variables Defined.