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

[Matt Wringe (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/GTNWSRP-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646073#comment-12646073 ] 

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.
                
> Problem with resourceId while rendering bookingMapPortlet over WSRP
> -------------------------------------------------------------------
>
>                 Key: GTNWSRP-269
>                 URL: https://issues.jboss.org/browse/GTNWSRP-269
>             Project: GateIn WSRP
>          Issue Type: Bug
>    Affects Versions: 2.1.0-GA
>         Environment: EPP5.2.0 CR01
> seamBooking demo from 2.2.0.GA.EPP520
>            Reporter: Michal Vanco
>            Assignee: Matt Wringe
>             Fix For: 2.1.1-GA
>
>         Attachments: seamBookingMap.txt
>
>
> Problem while serving resource for the portlet: selfv2./portalBookingDemo.bookingMapPortlet
> java.lang.IllegalArgumentException: GetResource needs a valid resource id.
> WSRP and PBR version weren't changed at CR01, that can be potentially caused by other change (& or double & issues at resources).
> And this error wasn't present at 5.2.0 ER06

--
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