Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1064245 - a4j:push is not working with WSRP
a4j:push is not working with WSRP
Status: CLOSED WONTFIX
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal, PortletBridge (Show other bugs)
6.1.1
Unspecified Unspecified
unspecified Severity unspecified
: CR01
: 6.2.0
Assigned To: Juraci Paixão Kröhling
Tomas Kyjovsky
:
Depends On: 1082651
Blocks:
  Show dependency tree / graph
 
Reported: 2014-02-12 04:54 EST by Petr Mensik
Modified: 2015-07-19 21:00 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-09-29 06:10:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Petr Mensik 2014-02-12 04:54:27 EST 
Nor Topics Context Usage or CDI push work in Showcase. No exception is thrown, there is nothing in the server log - however there should be a message that Atmosphere was able to install some servlets and filters so I guess this is the problem.

Steps to reproduce

1. Start JPP 6.1.CR1
2. Deploy Showcase
3. Start WSRP
4. Export Showcase as WSRP portlet
5. Try a4j:push under Ajax Action section
Comment 2 Boleslaw Dawidowicz 2014-02-13 05:25:52 EST 
Is it WSRP only or PBR in general?
Comment 3 Petr Mensik 2014-02-13 05:36:45 EST 
It seems to be caused by WSRP because portlet is running just fine in normal mode. However I think this is rather PBR problem, not WSRP one (all our WSRP tests are passing so WSRP probably somehow breaks PBR functionality).
Comment 4 Juraci Paixão Kröhling 2014-02-25 09:44:07 EST 
There was a change on #1063918 that probably affects this change. Would it be possible to re-check and see if your findings are still valid for this? On my tests, it was still not working, but as I mentioned on the other BZ, my current understanding is that the problem lies on PBR.
Comment 5 Juraci Paixão Kröhling 2014-04-15 13:28:18 EDT 
Status: for some requests, certainly for images and possibly for other types, RichFaces is building the URL with "/showcase-portlet" prefix on the URL, which is causing some 404s on the request that the consumer runs, which then relays this to the client. I'm still thinking this is probably a bug on PBR, but will get in touch with PBR experts to confirm this. The problem seems to be on the doRenderView method from org.jboss.portletbridge.application.PortletViewHandler, but I'm yet to confirm this.
Comment 7 Boleslaw Dawidowicz 2014-09-29 06:10:12 EDT 
Closing as won't fix. I created separate BZ for doc purposes

https://bugzilla.redhat.com/show_bug.cgi?id=1147470 for
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.