A cautious yes, however there are some things to think about.
1. Guice 1 wont work for concrete classes in OSGi unless its embedded as a private jar in both Social and Gadget bundles. IIRC Trunk is using Guice2 which I think is Ok. 2. The deployment of the servlets is likely to need some extra OSGi plumbing as at the moment the 4.1 spec doesn't have full servlet support. Its better in 4.2 and IIRC there are some extensions to handle full webapps bundled as wars, but not all OSGi frameworks have support. 3. I suspect you will have fun and games getting the dependency resolution sorted out if you intend to make many of the dependent jars bundles, so it might be better to make the private to start with but there are probably some basics that will have to come out (Java logging for instance is going to come from the framework bundle)
All that said, I would be interested in seeing patches for Shindig and OSGi.
Ian On 11 Nov 2009, at 16:28, Dave wrote:
Where I work we use OSGi in many of our products. We'd really like to see Shindig made available as a set of OSGi bundles that can be added into our existing Java web applications. At the same time, we also have applications that do not use OSGi, so we don't want to make Shindig depend on OSGi. Would Shindig committers be willing to accept a patch that makes the Shindig jars into OSGi bundles? For the OSGi experts in the house, what would you like to see in such a patch? I know that Atlassian has converted Shindig to OSGi bundles for use in JIRA 4.0, perhaps they could offer some advice here or perhaps even some code ;-) - Dave
