Comment #6 on issue 494 by kodemaniak: Guice Servlet Jar doesn't deploy in OSGi container(s)
http://code.google.com/p/google-guice/issues/detail?id=494
Using fragments to resolve this issue, however, has one ungly side effect. The com.google.inject.servlet package doesn't resolve anymore in eclipse. While this might be IDE specific (indeed the bundle works when deployed in an OSGi container), I think using fragments here is not the right solution. Correct me if I'm wrong, but Fragments are a means to extend the class path of a host bundle. The guice-servlet bundle, however, is not an extension of the guice bundle, but it is a bundle offering complementary functionality and uses(!) the guice bundle. Therefore I agree with ts.march that defining a rasonable API seems to be the only reasonable approach to resolve this issue. Using Fragments, to me, seems like a dirty fix. What is the reason for declaring some of the packages as bundle private when they are obviously required outside?
BTW, the issue in eclipse can easily be resoved by adding the guice-servlet jar explicitly to the class path of your own bundle. Then eclipse resolves the package.
-- You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en.
