Bug 974968 - a4j:push seems to not work in Showcase (Bug in PortletBridge)
Summary: a4j:push seems to not work in Showcase (Bug in PortletBridge)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: PortletBridge
Version: 6.1.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ER02
: 6.1.0
Assignee: Ken Finnigan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-17 09:32 UTC by Petr Mensik
Modified: 2015-07-20 01:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The PortletBridge extension code for RichFaces was modifying how the Push process worked on the server, which caused the a4j:push component to work incorrectly. The fix removes the PortletBridge extension to RichFaces for Push. a4j:push now works as expected.
Clone Of:
Environment:
Last Closed: 2013-11-07 14:24:36 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PBR-515 0 Major Closed Unable to start Atmosphere in portlet 2015-06-03 10:43:09 UTC

Description Petr Mensik 2013-06-17 09:32:58 UTC
There are currently two examples of a4j:push in the Showcase. Topics Context Usage example is not refreshing it's UUID by the Web Socket connection and the CDI Push doesn't work at all, the java.lang.IllegalArgumentException: pushTopic request parameter must be present is thrown. The same exception occurs if you try to refresh the Topics Context Usage page. 

Steps to reproduce

1. Deploy Showcase to JPP
2. Go to a4j:push under Ajax Action

Comment 1 Ken Finnigan 2013-06-18 20:09:29 UTC
Fixed as part of https://issues.jboss.org/browse/PBR-515 and released in PBR 3.2.1.Final, which is now used by GateIn master

Comment 2 Petr Mensik 2013-06-19 09:12:15 UTC
Yes, it's working in GateIn master with new PBR version. But I suppose we should wait to close this until it's verified in ER02.

Comment 3 Ken Finnigan 2013-06-19 13:31:41 UTC
Petr, this BZ is still open. It's only the PBR issue that is closed

Comment 5 JBoss JIRA Server 2013-08-16 18:34:48 UTC
Ken Finnigan <ken@kenfinnigan.me> updated the status of jira PBR-515 to Closed

Comment 6 Petr Mensik 2013-08-22 14:19:50 UTC
It seems to this issue is back with ER04 build. Both Topics Context Usage and CDI push doesn't work, however no exceptions are thrown and server log is empty.

Comment 7 Ken Finnigan 2013-08-26 20:05:01 UTC
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.

Not sure whether this problem should be tracked with this issue or a new BZ created?

Comment 8 Thomas Heute 2013-08-27 08:31:32 UTC
Petr, can you open a new BZ to follow the fixes independently ?

Looks like the first issue is fixed by a new version of PBR, while the second issue will require a new version of RF.

I am putting this one back as VERIFIED and will slightly change the title.


Note You need to log in before you can comment on or make changes to this bug.