Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1002971

Summary:	a4j:push is not working in Showcase
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Petr Mensik <pmensik>
Component:	PortletBridge	Assignee:	Nobody <nobody>
Status:	CLOSED UPSTREAM	QA Contact:	Tomas Kyjovsky <tkyjovsk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	epp-bugs, jpallich, oskutka
Target Milestone:	DR01
Target Release:	6.1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Atmosphere, the push library used by a4j:push, was attempting to use a WebSocket class that is no longer compatible with Red Hat JBoss Enterprise Application Platform. This caused a4j:push to throw server exceptions instead of producing a valid result. To work around the issue, disable WebSocket support in Atmosphere with the web.xml context-param directive: [source,XML] ---- <context-param> <param-name>org.atmosphere.useWebSocket</param-name> <param-value>false</param-value> </context-param> ----	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:28:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Mensik 2013-08-30 11:44:54 UTC

Both Topics Context Usage and CDI push doesn't work, however no exceptions are thrown and server log is empty.

Comment from Ken Finnigan

This is now a different issue.

It appears the classpath/modules available between EAP 6.1.0 and latest EAP 6.1.1 have changed, causing a ClassNotFoundException when running the a4j:push example of the showcase.

In JPP, failed network requests can be seen in the developer console of the browser. Attempting to issue one of those failed requests directly in the browser shows the ClassNotFoundException.

Issue has been raised with RichFaces: https://issues.jboss.org/browse/RF-13154.

Comment 2 Ken Finnigan 2013-11-07 15:16:14 UTC

Resolved with upgrade to RichFaces 4.3.4.Final

Comment 3 Petr Mensik 2013-12-17 13:31:20 UTC

Verified it's working with the upgraded version.

Comment 8 Red Hat Bugzilla 2025-02-10 03:28:26 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.