Eric, Thanks for initiating this thread. I spent a good amount of time debugging this issue before digging up this email chain. I followed Kevin's directions and, could get both Shindig's gadget (shindig/gadgets/files/container) and opensocial (shindig/gadgets/files/samplecontainer) to work.
I've captured the steps followed at http://pillvin.blogspot.com/2008/12/deploying-shindig-in-non-root-context.html Hope it helps. Regards, Vinod -----Original Message----- From: Citron, David [mailto:[email protected]] Sent: Thursday, December 18, 2008 8:52 AM To: [email protected] Subject: RE: shindig using non root context In spite of all this, I've been running Shindig at /shindig for months now under Jetty. The only thing I needed to do was set up a Jetty rewrite rule as follows: <Call name="addRule"> <Arg> <New class="org.mortbay.jetty.handler.rewrite.RewriteRegexRule"> <Set name="regex">/(social|gadgets)/(.*)</Set> <Set name="replacement">/shindig/$1/$2</Set> </New> </Arg> </Call> -Dave -----Original Message----- From: Eric Tschetter [mailto:[email protected]] Sent: Wednesday, December 17, 2008 6:54 PM To: [email protected] Subject: Re: shindig using non root context > Open source development is however also a demand driven development model, > so if this is an itch you want to scratch, patches are welcome! touché To be more clear about why I was concerned, I consider integration points a part of backwards compatibility in a release and I am wondering if a 1.0.0 release were made and then changes were made to how one integrates, could it be a minor version change or would it have to be a major? It seems like the change would either require support for the old integration method to be a minor or it would equate to a major release. That is, someone might not necessarily be able to just drop in a new JAR and have it work. Then again, the Apache APR documentation ("http://apr.apache.org/versioning.html";) seems to only talk about functional APIs and not necessarily configuration, so maybe I am making more out of it than it deserves. --Eric Tschetter Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
