[
https://issues.apache.org/jira/browse/RAVE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274431#comment-13274431
]
Erin Noe-Payne commented on RAVE-618:
-------------------------------------
I don't have a solution for this, but what I've found so far is -
In the gadgets.views init() function, it grabs the view parameters by doing a
json parse on url parameters.
Without pubsub required, the "view-params" argument looks like view-params:
"{"value":"yarrrgh","retVal":""}"
With pubsub required, it looks like: view-params:
"{"value":"yarrrgh","retVal":""}#rpctoken=nzZsoU"
I assume this means that pubsub is attaching an rpc token to the open gadget
url so that it can register with the hub. However, shindig isn't checking for
this hash token when it breaks up the url parameters, and it can't do a json
parse on the resulting string.
> Conflict between two features: open-views and pubsub-2
> ------------------------------------------------------
>
> Key: RAVE-618
> URL: https://issues.apache.org/jira/browse/RAVE-618
> Project: Rave
> Issue Type: Bug
> Affects Versions: 0.12
> Reporter: Chris Geer
> Priority: Blocker
> Attachments: open_views_demo.xml
>
>
> There seems to be some sort of conflict between the open-views feature and
> the pubsub-2 feature. If a gadget uses both features, you are unable to send
> view_params to your popup windows. Very rarely it will succeed which leads me
> to believe it's some sort of race condition somewhere.
> To reproduce this problem edit the open_views_demo.xml and simply add the
> <Require feature="pubsub-2"/> tag to the ModulePrefs. Sometimes I had to
> refresh my browser more than once for the new gadget definition to load if I
> manually copied the file to the running server (or restart the server).
> This is a major blocker for us right now.
--
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
