myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3610) Dynamically created ClientBehaviors do not call addComponentResource
Date Thu, 07 Feb 2013 03:01:15 GMT


Leonardo Uribe commented on MYFACES-3610:

Hi Richard

Yes, any change in that part must be done at spec level, because once the spec is out, we
can't do any changes without break binary compatibility.


> Dynamically created ClientBehaviors do not call addComponentResource
> --------------------------------------------------------------------
>                 Key: MYFACES-3610
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.1.7
>            Reporter: Kennard Consulting
>         Attachments:
> I'm creating this as a JIRA issue so that I can attach a test case. However it behaves
the same on Mojarra as on MyFaces so possibly it is 'by design'?
> My question is this:
> * If I dynamically create UIComponents using Application.createComponent, I find they
automatically add any dependent resources (JS/CSS) to the h:head. This is fantastic.
> * If I dynamically create ClientBehaviours using Application.createBehavior, no dependent
resources get added.
> Am I supposed to add such resources manually? For example:
>    UIOutput js = new UIOutput();
>    js.setRendererType("javax.faces.resource.Script");
>    js.getAttributes().put("library", "mylibrary");
>    js.getAttributes().put("name", "bar.js");
>    FacesContext context = FacesContext.getCurrentInstance();
>    context.getViewRoot().addComponentResource(context, js, "head");
> If so, how am I supposed to know what they are? For example, if I am dynamically adding
an AjaxBehavior the exact name of the JavaScript file depends on which JSF implementation
I am using.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message