[
https://issues.apache.org/jira/browse/SHINDIG-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Baxter updated SHINDIG-1707:
---------------------------------
Description: When Shindig renders views of gadgets of type URL, certain
parameters are passed that should allow the application at that URL to request
the javascript for the features the gadget uses. (See
http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#rfc.section.3.4)
Today you get the host of the server and the features the gadget uses, but
you do not get the path to the JS servlet. Since the servlet can be configured
in the web.xml it is possible that the path is different depending on the
instance. (was: When Shindig renders views of gadgets of type URL, certain
parameters are passed that should allow the application at that URL to request
the javascript for the features the gadget uses. Today you get the host of the
server and the features the gadget uses, but you do not get the path to the JS
servlet. Since the servlet can be configured in the web.xml it is possible
that the path is different depending on the instance. )
> Path To JS Servlet Not Passed As Param For Gadgets Of Type URL
> --------------------------------------------------------------
>
> Key: SHINDIG-1707
> URL: https://issues.apache.org/jira/browse/SHINDIG-1707
> Project: Shindig
> Issue Type: Bug
> Reporter: Ryan Baxter
>
> When Shindig renders views of gadgets of type URL, certain parameters are
> passed that should allow the application at that URL to request the
> javascript for the features the gadget uses. (See
> http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#rfc.section.3.4)
> Today you get the host of the server and the features the gadget uses, but
> you do not get the path to the JS servlet. Since the servlet can be
> configured in the web.xml it is possible that the path is different depending
> on the instance.
--
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
