myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-2687) Make sure jsf.js is included if client behaviors are rendered
Date Thu, 29 Apr 2010 22:01:53 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862440#action_12862440
] 

Leonardo Uribe commented on MYFACES-2687:
-----------------------------------------

Note that what we are doing right now is call ResourceUtils.writeScriptInline(facesContext,
writer, ResourceUtils.JAVAX_FACES_LIBRARY_NAME, ResourceUtils.JSF_JS_RESOURCE_NAME) when it
is used jsf.util.chain().

> Make sure jsf.js is included if client behaviors are rendered
> -------------------------------------------------------------
>
>                 Key: MYFACES-2687
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2687
>             Project: MyFaces Core
>          Issue Type: Task
>          Components: JSR-314
>    Affects Versions: 2.0.0
>            Reporter: Jakob Korherr
>            Assignee: Jakob Korherr
>
> When attaching a ClientBehavior ( != <f:ajax>) to e.g. a <h:commandButton>,
jsf.util.chain() is implicitly used by the <h:commandButton> when rendering the ClientBehavior.
> However if no <f:ajax> stuff is on the current page or jsf.js is not included manually
by <h:outputScript library="javax.faces" name="jsf.js" />, we will get a JavaScript
error saying "jsf is not defined", because jsf.util.chain() is used, but jsf.js is not there!

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


Mime
View raw message