[gatein-issues] [JBoss JIRA] (GTNWSRP-269) Problem with resourceId while rendering bookingMapPortlet over WSRP

[ https://issues.jboss.org/browse/GTNWSRP-269?page=com.atlassian.jira.plugi... ] Matt Wringe commented on GTNWSRP-269: ------------------------------------- Ok, so this is related to the fix in JBEPP-1358, but the fix in JBEPP-1358 isn't really the issue, its now just causing this issue to be exposed. What was happening before the patch was that in a query string if '&' was used instead of '&' then it would treat the parameter name as 'amp;' + actual_parameter_name. When the portal would check what type of action to take, it looks for the 'portal:type' parameter. Prepatch it would not find this value (since its 'amp;portal:type' and not 'portal:type') and a null value would cause action to render the portlet instead of fetching a resource. So in this case its not doing the right thing. Postpatch, it now gets that the action should be to fetch a resource, but then there is something wrong happening here where it can't get the proper resourceId. Looking deeper into issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira