Tim, Currently we've done something similar, except that we took the shindig war-file, and built the equivalent of a webapp, that we surface to an embedded jetty. We don't do the servlet mapping, we just take it and expose it through the embedded jetty.
Personally I'm new to using OSGi (3 months), and most of my work to date hasn't needed a deep thorough understanding of it, but with my limited knowledge I believe you avoided what we think we want to do: a. Modify maven so that it can produce OSGi bundles for each of the 4 shindig jars (social-api, server, gadget, and common). b. These bundles would include package import directives which would result in the shindig dependencies getting picked up from OSGi. c. Use internal OSGi extensions to surface the OpenSocial servlets to our web application. Why did you avoid using 4 bundles instead of one? Also, Ian mentioned issues with Guice 1 vs. Guice 2. Can anyone elaborate on the technical issues? Thanks,
