[
https://issues.jboss.org/browse/RF-12509?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12509:
---------------------------------
The sample in {{dev-examples/core-demo}} works fine.
----
The issue is caused by invalid {{jsf.js}} (Production version) served, which does not
contain {{var mojarra = mojarra || {};}} definition.
In particular, the issue does not happen when running Metamer in Development stage. When
switched to Development, {{jsf-uncompressed.js}} is served, which contains this
definition.
----
Note that {{core-demo}} works because original Mojarra 2.1.7 resources are served.
Metamer does not work because there are {{jboss-jsf-api-*.jar}} packaged with
application.
Command link with disabled ajax doesn't work
--------------------------------------------
Key: RF-12509
URL:
https://issues.jboss.org/browse/RF-12509
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core, regression
Affects Versions: 4.3.0.Milestone2
Environment: RichFaces 4.3.0-SNAPSHOT
Metamer 4.3.0-SNAPSHOT
Mojarra 2.1.7
JBoss AS 7.1.2.Final-redhat-1
Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux
Firefox 15.0.1 @ Linux x86_64 / Chrome 22.0
Reporter: Pavol Pitonak
Assignee: Lukáš Fryč
Priority: Blocker
Fix For: 4.3.0.Milestone2
# deploy Metamer and open
http://localhost:8080/metamer/faces/components/a4jAjax/hCommandLink.xhtml
# set disabled=true
# type something into input
# click "Submit" link
result:
* HTTP request is expected but no request is fired
* works fine in Chrome 22
* works fine with RichFaces 4.3.0.M1 with all browsers
* "ReferenceError: mojarra is not defined" in Firefox console
--
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:
http://www.atlassian.com/software/jira