On Tue, Dec 16, 2008 at 10:30 AM, Kevin Brown <[email protected]> wrote: > On Mon, Dec 15, 2008 at 9:14 PM, Carmen Sarlo <[email protected]> wrote: > >> Hello, >> >> We want to serve shindig using something other then the root context (/). >> Say something like (/shindig). I see the examples are hard coded. I can >> live with that, but what about the rest of the code? What is needed to get >> this working to serve other then root context? We will be using the java >> implementation of shindig. > > > It should work just fine on any context, but there are quite a few urls you > have to update. There's an open issue to migrate all of this to one place, > but nobody's ever gotten around to it. > > Make sure you update all the paths in the container config > (trunk/config/container.js) as well as the language-specific configuration > file (for java, it's trunk/java/common/config/shindig.properties). > > Once you've got that, you should be able to set web.xml appropriately.
Why isn't fixing this a part of the "release" version of Shindig? I would assume that ease of integration would be a high priority in something that is supposed to be released for external consumption. Also, should people looking to integrate against Shindig be integrating against trunk? I'm assuming the paths in your message should be pointing to the release branch. I know I wouldn't be very happy if I were to start integrating against Shindig because I heard it was going to release a stable version only to find out that the version I integrated against is the unstable dev branch. Not trying to troll, it just struck me as odd that there was no mentioning of fixing this integration issue in any of the release threads. --Eric Tschetter
