shindig-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Jones (JIRA)" <>
Subject [jira] [Updated] (SHINDIG-1873) Incorrectly parsed moduleId in TokenRequestData
Date Thu, 20 Sep 2012 08:07:07 GMT


Matt Jones updated SHINDIG-1873:

    Attachment: fix-SHINDIG-1873-2-bug.patch

New patch per review.
> Incorrectly parsed moduleId in TokenRequestData
> -----------------------------------------------
>                 Key: SHINDIG-1873
>                 URL:
>             Project: Shindig
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: 2.5.0-beta4
>            Reporter: Matt Jones
>         Attachments: fix-SHINDIG-1873-2-bug.patch, fix-SHINDIG-1873-bug.patch
> When a gadgets:token RPC request is made the gadget's module ID is encoded with the gadget's
URL in the form:
> [gadget URL]#[module ID] (features/src/main/javascript/features/container.util/util.js
line 191)
> However, when the module ID is parsed out by the container, it seems to expect it in
the form:
> [gadget URL]#moduleId=[moduleId] (GadgetsHandler.TokenRequestData, line 575)
> This means moduleId is never parsed and the RPC request always returns a moduleId of
> The comment above the container code seems to imply that the JS encoding is correct and
therefore the container's code is at fault.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message