Ok that's the correct path. I'll see if I can reproduce
>-----Original Message----- >From: Chris Geer [mailto:[email protected]] >Sent: Friday, May 25, 2012 12:59 PM >To: [email protected] >Subject: Re: PubSub & RPC Token > >The rpcToken thing might be a red herring as you said. This was the patch I >applied > >ndex: >extras/src/main/javascript/features-extras/org.openajax.hub-2.0.5/iframe.js >=========================================================== >======== >--- >extras/src/main/javascript/features-extras/org.openajax.hub-2.0.5/iframe.js >(revision >1340294) >+++ >extras/src/main/javascript/features-extras/org.openajax.hub-2.0.5/iframe.js >(working >copy) >@@ -398,8 +398,12 @@ > } else { > iframe.onload = >function(){window[params.IframeContainer.onGadgetLoad]();}; > } >- iframe.src = params.IframeContainer.uri + >- "#rpctoken=" + securityToken + tunnelText + idText; >+ >+ var uri = params.IframeContainer.uri; >+ var hashIdx = uri.indexOf('#'); >+ var joinToken = (hashIdx === -1)?'#':'&'; >+ >+ iframe.src = uri + joinToken + "rpctoken=" + securityToken + >tunnelText + idText; > } > > // If the relay iframe used by RPC has not been loaded yet, then we >won't have unload protection > >On Fri, May 25, 2012 at 9:54 AM, Noe-Payne, Erin A. ><[email protected]>wrote: > >> Chris, >> >> I would think it's not surprising that the rpc token is present? Gadgets >> use rpc for more than just pubsub, but I'm not sure about that. I'll take a >> look on my local build. >> >> Also, which iteration of the shindig patch do you have? The most recent >> version applies to the openajax.hub feature, rather than to the url params >> feature, so make sure you are on that. >> >> Erin >> >> >-----Original Message----- >> >From: Chris Geer [mailto:[email protected]] >> >Sent: Friday, May 25, 2012 12:38 PM >> >To: dev >> >Subject: PubSub & RPC Token >> > >> >I ran into an odd issue today regarding pubsub-2 again. In my modules >> where >> >I'm using pubsub-2, everything is working great. The problems comes in my >> >modules that aren't using pubsub-2, they will no longer load in canvas, >> and >> >won't reload when coming back to home view. After doing a little digging I >> >saw there was a failed network connection (using Chrome's developer >tools) >> >when the gadget tried to load in canvas mode. It was the Ifr request to >> >/gadgets to load the gadget.xml file. What seemed odd was in looking at >> the >> >request url it included a #rpcToken element even though that gadget >didn't >> >declare pubsub-2 in it's requirements. As soon as I added in the pubsub-2 >> >feature it all worked great. The gadget doesn't use pubsub-2 anywhere in >> >it's definition or js. This happened on two gadgets and adding in the >> >feature solved it on both so it wasn't isolated to a single gadget. >> > >> >BTW - I am currently running Rave .12-SNAPSHOT against Shindig >> >2.5.0-SNAPSHOT with Erin's pubsub-2 patch. I realize this puts me in >> >"unknown" territory a bit but I thought I'd ask anyway. Any thoughts? >> > >> >Chris >>
