Which container are you using? Jetty works automatically out of the
box (because it sets jetty.port variable)
You can try setting the value of the environment variable shindig.port
to 8086. This can be done via command line arguments or in the web.xml
section like this:
<context-param>
<param-name>system.properties</param-name>
<param-value>
shindig.host=localhost
aKey=/shindig/gadgets/proxy?container=default&url=
shindig.port=8086
</param-value>
</context-param>
On Wed, Jan 12, 2011 at 11:50 AM, Matthias Luft <[email protected]> wrote:
> Hi,
>
> first of all, I have to confess that I'm not really into shindig but am
> to fix a certain issue with shindig.
>
> I try to run a gadget on a customized install of shindig:
> http://localhost:8086/gadgets/ifr?url=http://localhost:8081/Gadget.xml
>
> When I render the gadget, it tries to include additional javascript from
> localhost:8080:
> [snip]<script
> src="http://localhost:8080/gadgets/js/core:rpc.js?container=default&nocache=0&debug=0&c=0&v=d231426e6cc5fbec0e450ad1b77a3a6c";></script>[snip]
>
> Unfortunately, shindig does not listen on localhost:8080 in our setup. I
> tried different configurations in container.js and search for
> documentation about this issue, but no luck. So the main questions would be:
> * Can this location be configured in container.js?
> * Where must container.js be located (filesystem/war file speaking)
> * If not, where can I configure the host for the additional JS?
>
> Thx & best regards,
> Matthias
>
>
--
Paul Lindner -- [email protected] -- linkedin.com/in/plindner
