Hi, Can someone from the Guice core development team please take a look at http://n2.nabble.com/Using-Guice-with-JAX-RS-tt1127230.html
I've integrated Guice into Jersey (the reference implementation for JAX-RS) but the implementation is fragile. If you read that discussion thread you will likely see a lot of potential RFEs for Guice to fix this. One topic I had in mind is the fact that Jersey knows how to inject some classes, Guice knows how to inject others, but they cannot share that information with one another. Ideally I want Guice to inject all the classes it knows and ask Jersey how to inject some type before deciding to throw ConfigurationException. To be fair, this use-case is rather ugly. It isn't clear what should happen if a class is marked up using Guice annotations but Guice doesn't know how to configure it because it isn't bound in the Module. Jersey would be able to inject it but it will end up ignoring the Guice annotations. I want to avoid misleading the user into thinking Guice took all his annotations into consideration when in fact it did not. Anyway, I could really use a second set of eyes to give me feedback. Thank you, Gili --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en -~----------~----~----~----~------~----~------~--~---
