Have been unable to reproduce this error with ER02 or GateIn master using Firefox 16 and Chromium 20 on Ubuntu.

Filip, can you confirm the environment and browser in which you encountered the error?

Just tested with ER03 on Chromium 20 and Firefox 16 on Ubuntu, both browsers don't experience this problem.

I tested it on RHEL6 with Firefox 10esr and Fedora17 with Chrome 21 and Firefox 15. JSF local portlet works fine, but two buttons in remote portlet don't work.

I tried both ER02 and ER03.

Filip, can you be more specific on what buttons didn't work ? And what "doesn't work" mean in that context (doesn't do anything, any stacktrace...).

Thanks.

Echo and reset buttons didn't work as I mentioned in description, reload button works fine. So when you click on echo or reset button nothing happens (and no exception is thrown).

Filip, are there any errors in the browser console? Such as missing files or JS errors?

I'd be very surprised if it didn't work and there were no errors anywhere.

When site with remote portlet is loaded, browser console shows following CSS warning:

"Expected declaration but found '!'.  Skipped to next declaration."
"Unknown property 'zoom'.  Declaration dropped."

But while pressing echo or reset buttons, there were no errors.

Using browsers in Fedora 17 and the server running on my Ubuntu, both Firefox 16 and Chrome 23 worked fine with the JSF2 portlet over WSRP.

Filip, it looks like its an issue with your JPP install on Fedora.

Ken, I tried it also remotely on RHEL6 machine in lab to make sure it is not due to my local JPP install - same results as my Fedora.

Hi,

I was able to reproduce the issue with Ubuntu on FF16. Steps:
1. Took a clean jboss-jpp-6.0.0.ER03.zip (md5sum b1d2a836f1a5bace9e1742ef82e1fd67), unzip
2. Downloaded and built jbossportletbridge-3.1.0.Final.zip
3. Copied /examples/jsf2portlet/target/jsf2portlet.war into standalone/deployments
4. run the JPP, go to WSRP consumer config page, enable selfv1 and selfv2 consumers
5. Go to administration -> aplication registry -> import portlets
6. On some page, add the portlet from Selfv1 producer category, and the portlet from Selfv2 producer category.
7. Portlet from Selfv2 works as expected, Portlet from Selfv1 does not respond.

From the reproduction steps Viliam has provided I can see that the issue appears to be with the jsf2portlet over WSRP for v1, but v2 works fine.

My understanding of WSRP is quite basic, but as the jsf2portlet uses Ajax techniques within the two buttons that don't work, I believe that support for ResourceRequest in WSRP v1 is patchy at best and that anyone using Ajax portlets would only use WSRP v2.

If we are meant to verify Ajax portlets against WSRP v1, I'd like someone to confirm that the same portlet from PortletBridge 2 (as we're talking JSF 1) works ok with WSRP v1 in EAP 5.2.  If it doesn't, I see no reason to try and resolve this.

Is it a regression of a test that worked in 5.2? As it seems that it is working with v2 unless it is regression from 5.2 we would prefer to close it as won't fix.

It's not a regression as JSF 2 wasn't supported in 5.2 as far as I'm aware. I think we should state that WSRP v1 is still supported for people who are using it but no one should start a new project with it if they have a choice and that JSF/RF support is only supported on WSRP 2.

Hi Bolek,
I wouldn't say that it's a regression since jsf2 wasn't even supported at EPP 5.2, it's new for 6.x.
And for WSRP & PBR - as I recall, it was tested only with v2 and I agree to close this one if it works fine with v2. I would say that ajax and other portlet stuff wasn't well supported with v1, that's why v2 was created.
I don't even see any serious reason why would anyone use v1 if v2 is available.
My vote is to close the issue and support only wsrp v2 for jsf2 & rf4.

Looks like we are all in agreement then :)