[
https://issues.apache.org/jira/browse/MYFACES-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-2687:
------------------------------------
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.1-SNAPSHOT
Resolution: Fixed
> 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: Leonardo Uribe
> Fix For: 2.0.1-SNAPSHOT
>
> Attachments: MYFACES-2687-core.patch, MYFACES-2687-shared.patch
>
>
> 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.
