Red Hat Bugzilla – Bug 974968
a4j:push seems to not work in Showcase (Bug in PortletBridge)
Last modified: 2015-07-19 21:00:59 EDT
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
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
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.
Petr, this BZ is still open. It's only the PBR issue that is closed
Ken Finnigan <email@example.com> updated the status of jira PBR-515 to Closed
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.
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?
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.