You can also manually configure the list of methods too.
On Tue, Jul 31, 2012 at 11:19 AM, Henry Saputra wrote:
> Could you try to modify your container file to set
>
> "osapi" : {
> // The endpoints to query for available JSONRPC/REST services
> "endPoints" : [ "//%host%${CONTEXT_ROOT}/
Could you try to modify your container file to set
"osapi" : {
// The endpoints to query for available JSONRPC/REST services
"endPoints" : [ "//%host%${CONTEXT_ROOT}/rpc" ]
}
to point to shindighost.com?
- Henry
On Tue, Jul 31, 2012 at 10:52 AM, daviesd wrote:
> They don't live on di
They don't live on different hosts, they are just gotten there by different
dns. For example the javascript request looks like:
https://prefix.shindighost.com/gadgets/js/rpc.js?nocache=1&c=1&container=def
ault
However the server shouldn't go through prefix.shindighost.com. I really
want it to g
Looks like the rpc call to system.listMethods is called in
RenderingGadgetRewriter and ConfigInjectionProcessor to execute the
gadgets.config.init
For both scenario looks t will try to call itself using the request
"host" header.
Doug, so in your setup the js serving endpoint live in different ho
I just recently noticed a behavior with the rpc interface that I have
discovered in the 11th hour and we are ready to rollout, so any input asap
is appreciated.
Shindig at some point makes an rpc call back to itself for listMethods. I
thought this use to happen upon startup, but I might be wrong.
