Yes, I also think that it is not a NetUI problem. And the thing is that exposed portlet is not a JSR 168 portlet. It is a BEA Portal Page Flow Portlet.
IMHO, the problem is in the way how JBoss WSRP consumer processes links with parameters. If you look at the WSRP requests/responses between JBoss Consumer and BEA Producer, when the link is pressed, then WSRP performBlockingAction method is called with the action specified on the link, but without parameters. Best regards, Andrey View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045033#4045033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045033 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
