Bug 1064245 - a4j:push is not working with WSRP
Summary: a4j:push is not working with WSRP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal, PortletBridge
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR01
: 6.2.0
Assignee: Juraci Paixão Kröhling
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On: 1082651
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 09:54 UTC by Petr Mensik
Modified: 2015-07-20 01:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-29 10:10:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Mensik 2014-02-12 09:54:27 UTC
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 10:25:52 UTC
Is it WSRP only or PBR in general?

Comment 3 Petr Mensik 2014-02-13 10:36:45 UTC
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 14:44:07 UTC
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 17:28:18 UTC
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 10:10:12 UTC
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.