[
https://issues.apache.org/jira/browse/SHINDIG-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560634#action_12560634
]
John Hjelmstad commented on SHINDIG-18:
---------------------------------------
What Kevin says is right - there was a bit of confusion in commmunication here.
The setprefs.js lib will be packaged by the JavaScript servlet in Shindig with
all its dependencies included. They need not be listed in the list of libs. In
fact ,this is the proverbial feature, not a bug, in that this approach
consolidates all JS serving in a single file rather than requiring several HTTP
requests, one per feature bundle.
My understanding was that you found type=url gadget functionality to simply not
be working. Is that true? If so, could you give any more details on the
behavior you observed? That's what I'm signed up to fix :)
> Dependent javascript libraries are not being passed in http-get "libs="
> parameter
> ---------------------------------------------------------------------------------
>
> Key: SHINDIG-18
> URL: https://issues.apache.org/jira/browse/SHINDIG-18
> Project: Shindig
> Issue Type: Bug
> Environment: Url content type gadget loaded on Shindig container
> (current build)
> Reporter: OpenSocial QA Team
>
> To reproduce the bug:
> - Create a url content type gadget.
> - Add Request feature="setprefs" to the gadget
> - Check the url parameters passed and you will see that the container is
> passing only the setprefs.js as "libs=" parameter.
> It should also include the tree of dependent javascript libraries as libs=
> parameters of the http-get request
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
