I think this may be worth a note in the documentation, as WSRP support may grow more important in the future. Is there any plan to upgrade to WSRP 2.0? Thanks.
On Mon, Jan 19, 2009 at 5:16 PM, uiterlix
<do-not-reply@jboss.com> wrote:
We finally found the error.
If you look at the following URL, you'll find it contains a small mistake:
| ?WSRPProducer=Application WSRP producer&WSRPPortletHandle=/Application.InboxPortlet&WSRPPortletState=&WSRPRegistrationHandle=11&WSRPRegistrationState=&WSRPMode=wsrp:view&WSRPWindowState=wsrp:normal&WSRPQualifiedName=g_9bcea8ab_df1d_4ced_b0f1_453faf9f2c10&WSRPIsAnonymous=False&WSRPAction=wsrp%5Frewrite%3Fwsrp%2DurlType%3DblockingAction%26amp%3Bwsrp%2DinteractionState%3DJBPNS%
| 5F%2Fwsrp%5Frewrite
|
It contains "%26amp%3B" which is an encoded "&". This happend because when you obtain the render/action url from the PortletResponse, JBoss returns:
| wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-interactionState=JBPNS_
|
I don't quite understand why the url obtained from the PortletResponse contains an URL that has already escaped the "&", but undoing this escaping by replacing the "&" with just "&" solves the problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203003#4203003
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203003
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user