[jira] [Resolved] (SHINDIG-1777) OpenViews / pubsub-2 conflict

["Erin Noe-Payne (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SHINDIG-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erin Noe-Payne resolved SHINDIG-1777.
-------------------------------------

    Resolution: Fixed

Fixed with 1777.patch
                
> OpenViews / pubsub-2 conflict
> -----------------------------
>
>                 Key: SHINDIG-1777
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1777
>             Project: Shindig
>          Issue Type: Bug
>          Components: Javascript 
>    Affects Versions: 2.5.0-beta1
>            Reporter: Erin Noe-Payne
>            Priority: Minor
>              Labels: openviews, pubsub, rpctoken
>             Fix For: 2.5.0-beta1
>
>         Attachments: 1777.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> To reproduce: 
> 1) Create a gadget that requires both open-views and pubsub-2 features.
> 2) Make a call to gadgets.views.openGadget(), passing a viewParams object
> 3) In the newly opened gadget, make a call to gadgets.views.getParams(). You will receive an empty object, regardless of what was passed as a parameter.
> What's happening?
> 1) It looks like pubsub-2 appends an rpc token to the open gadget url in the form of #rpctoken=nzZsoU
> 2) The resulting url param for views looks like this -  view-params: "{"value":"yarrrgh","retVal":""}#rpctoken=nzZsoU"
> 2) In the views feature, views.js, line 120: The param goes through json.parse, which fails and returns an empty object
> This will probably affect more than just the openviews feature.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira