No, there's not an easy way to run in a non-root context with the generated WAR. Generally speaking you're going to want to integrate with your own code which almost always means generating your own war with your own resources.
I'd love to see a maven archetype for creating this. It's just something that we haven't done yet. On Tue, Dec 7, 2010 at 4:03 AM, Folke Mitzlaff <[email protected]>wrote: > Hi, > > I'm trying to run shindig on a tomcat 5.5 servlet container together with > an other web application with a non root context path (e.g. > '/shindig-server'). > > All open social urls are mapped to '/' with an apache web server using > mod_proxy (e.g. > '/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1' is proxied to > '/shindig-server/gadgets/js/core:rpc:pubsub:shindig-container.js?c=1&debug=1'). > > The main problem is that shindig's default set up is configured to run in > the root context. Accessing the url given above yields status 400 with the > message 'The request sent by the client was syntactically incorrect (Js Uri > path invalid, expected prefix: /gadgets/js, is: > /shindig-server/gadgets/js/core:rpc:pubsub:shindig-container.js).' > > I finally succeeded to get the set up running by updating > 'shindig.properties' and 'container.js' within the deployed file > 'shindig-common-2.0.0.jar'. But this is cumbersome. So my question is: Is > there a standard way for configuring shindig's context path, e.g. by setting > a context parameter in tomcat's context.xml or placing a configuration file > in some place? > > > Any help is appreciated! > > .folke > -- Paul Lindner -- [email protected] -- linkedin.com/in/plindner
