Bug 974968
Summary: | a4j:push seems to not work in Showcase (Bug in PortletBridge) | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | Petr Mensik <pmensik> |
Component: | PortletBridge | Assignee: | Ken Finnigan <kfinniga> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.0 | CC: | bdawidow, epp-bugs, jsedlace, theute |
Target Milestone: | ER02 | ||
Target Release: | 6.1.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-07 14:24:36 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-06-17 09:32:58 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 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 <ken> 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. |