Bug 901013 (JBPAPP6-1048) - JSF issue breaking RF4 support for EPP
Summary: JSF issue breaking RF4 support for EPP
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBPAPP6-1048
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: EAP 6.0.1
Assignee: Stan Silvert
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-05 13:18 UTC by Thomas Heute
Modified: 2014-06-28 12:48 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-08 09:40:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 900863 0 urgent CLOSED Memory leak due to JSF 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 901033 0 high CLOSED Upgrade to Mojarra 2.1.13 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker AS7-5670 0 Major Resolved jboss-jsf-api contains invalid jsf.js 2013-07-17 15:58:24 UTC
Red Hat Issue Tracker JBPAPP6-1048 0 Blocker Closed JSF issue breaking RF4 support for EPP 2013-07-17 15:58:23 UTC

Internal Links: 900863 901033

Description Thomas Heute 2012-10-05 13:18:58 UTC 
project_key: JBPAPP6

For RichFaces 4 support in EPP6 we are facing the following issue when running on top of EAP 6.0.1 ER2
http://java.net/jira/browse/JAVASERVERFACES-2471

The issue has been fixed in Mojarra JSF 2.1.12 and beyond.

We tested with Mojarra JSF 2.1.13 and it indeed fixed our issue.

Without this upgrade in EAP, we won't be able to do Ajax calls in JSF portlets and we would have to patch ourself JSF which is something we want to avoid as it may bring support confusion. It's a blocker for EPP6 which will be based on EAP 6.0.1

We've seen other cases requiring a newer version of JSF, I will link them here.

Note that Stan already has a JAR available.
Comment 1 Thomas Heute 2012-10-05 13:20:28 UTC 
Link: Added: This issue relates to JBPAPP-9855
Comment 2 Thomas Heute 2012-10-05 13:22:37 UTC 
Link: Added: This issue relates to AS7-5670
Comment 3 Pavel Slavicek 2012-10-08 10:28:34 UTC 
Labels: Added: eap601-qe-triage
Comment 4 Anne-Louise Tangring 2012-10-08 13:54:49 UTC 
Approved for EAP 6.0.1
Comment 5 Anne-Louise Tangring 2012-10-08 13:54:49 UTC 
Labels: Removed: eap601-qe-triage
Comment 6 Stan Silvert 2012-10-08 20:13:58 UTC 
Git Pull Request: Added: https://github.com/jbossas/jboss-as/pull/3208
Comment 7 Fernando Nasser 2012-10-09 20:33:51 UTC 
Ales, please do not forget to create an "Upgrade to...." JIRA for the JAF 2.1.13 upgrade and link it to https://issues.jboss.org/browse/JBPAPP-9721

This upgrade JIRA should "includes" the fix for https://issues.jboss.org/browse/JBPAPP-10134

Thanks for looking into this issue!
Comment 9 Stan Silvert 2012-10-10 17:20:31 UTC 
Link: Added: This issue relates to JBPAPP-10158
Comment 11 Fernando Nasser 2012-10-10 20:04:55 UTC 
Thanks Stan.  I linked the 10158 to the upgrades tracker one, so all is fine.
Comment 12 Fernando Nasser 2012-10-11 13:07:27 UTC 
JSF upgraded to 2.1.13  (api to 2.0.7.Final)
Comment 13 Thomas Heute 2012-10-11 13:44:09 UTC 
Thanks everyone !
Comment 14 Misty Stanley-Jones 2012-11-05 04:06:48 UTC 
Release Notes Docs Status: Added: Not Required
Comment 15 Jitka Kozana 2012-11-08 09:40:43 UTC 
Verified during EAP 6.0.1.ER3, closing.
Comment 16 Anne-Louise Tangring 2012-11-13 20:18:21 UTC 
Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW
Note You need to log in before you can comment on or make changes to this bug.