We JUST solved this same issue this week. See my earlier threads. http://mail-archives.apache.org/mod_mbox/shindig-dev/201103.mbox/%3cE3FA [email protected]%3e
http://mail-archives.apache.org/mod_mbox/shindig-dev/201103.mbox/%3c9E24 [email protected]%3e We pull down all the shindig maven artifacts and build our own webapp (don't try to use the war downloadable war file and patch it). We took container.js and made our own mycontainer.js. We then overrode all paths to have /shindig in front (maybe a dozen places). Place this file at java/resources/containers/default/mycontainer.js in YOUR project. Also override shindig.properties and put that at resources/shindig.properties. In that file reference your new container. shindig.containers.default=res://containers/default/container.js,res://c ontainers/default/mycontainer.js. Also put /shindig out in front of the proxy-url and concat-url in there. This will get you up and running in a different webapp context (/shindig). Now if you want to run shindig server in one domain and your container (webapp) in another (which is recommended) you'll want to install some sort of proxy on the client side. We used the proxy target in UrlRewriteFilter and configured it as follows <rule match-type='wildcard'> <from>/shindig/**</from> <to type="proxy">http://localhost:9090/shindig/$1</to> </rule> This will take all client request to /shindig and proxy them to the shindig server. Also check out https://issues.apache.org/jira/browse/SHINDIG-1502 if you are using shindig 3.0. We had to do this to get the security tokens to work in a dev environment for now. Hope this help. Feel free to contact me if you have questions. doug -----Original Message----- From: David A. Jafari [mailto:[email protected]] Sent: Monday, April 04, 2011 5:41 PM To: [email protected] Subject: Configuration Documentation Hey guys, I'm playing around with Shindig to see if it makes sense to integrate with my co's enterprise app. I've been trying to reconfigure the root paths to take into account the content root of our web-app, but the configuration options for doing so do not seem to be used. I found a sample shindig.properties file from http://svn.apache.org/repos/asf/shindig/trunk/java/common/conf/ and thought the shindig.content-rewrite.concat-url property was what I was looking for. Modifying this value had no effect and after looking through the shindig-2.0.0 source code, I don't think it is even being used. So I have two questions: 1) Where might I find documentation related to the configuration properties for Shindig, if any? 2) Specifically, which property could I use to rewrite urls such that they respect a non-root context? Thanks, Dave Jafari
