[
https://issues.apache.org/jira/browse/SHINDIG-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620205#action_12620205
]
Chris Chabot commented on SHINDIG-492:
--------------------------------------
Thats the same features, but the container side (for the rpc service) indeed,
if you look at partuza for instance it has:
<script type="text/javascript"
src="http://modules.partuza.nl/gadgets/js/rpc.js?c=1";></script>
Which includes the container side JS code for the rpc service ... again that's
nothing in the neighbourhood of having a 'SNS', and quite the same between
versions though :)
> Config option "container_config" is ignored
> -------------------------------------------
>
> Key: SHINDIG-492
> URL: https://issues.apache.org/jira/browse/SHINDIG-492
> Project: Shindig
> Issue Type: Bug
> Components: Gadget Rendering Server (PHP)
> Reporter: Artemy Tregubenko
> Assignee: Chris Chabot
> Priority: Minor
>
> Config file has option "container_config", which allows to use some other
> config file instead of container.js. However when GadgetContext creates
> ContainerConfig instance in instanceContainerConfig method, it uses
> "container_path" option for initialization, thus javascript options are
> always loaded from /shindig/config/container.js file. This file can be
> overwritten during shindig update, thus it's not a good idea to customize it,
> so there's no good way to customize javascript options.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
