[
https://issues.apache.org/jira/browse/SHINDIG-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620189#action_12620189
]
Chris Chabot commented on SHINDIG-492:
--------------------------------------
Oh? That's news to me, as far as i am aware (and i'm pretty familiar with the
source tree of shindig) there's only a samplecontainer.html file, which works
with both the php and java versions of shindig .. and no 'real sns code'.
Both sides have the gadget renderer, proxy, oauth bits and a social-api
interface (+ json meta data service, etc), and no SNS code...
What exactly are you referring too? Or do you mean the
javascript/samplecontainer code? That really does work with both versions, but
i would hardly call that 'SNS code', it's more a simple & static example..
> 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.
