Sundar,
The implementation needs to be a lot more involved than this. My own
implementation has the following extra pieces:
1) a ComponentProvider
2) a InjectableProvider
3) a GuiceServlet. You provide an annotation which might be a better
idea, but you need to allow users to link to an existing Injector
instead of assuming your own code will always create one. For example,
if I want to use warp-persist with Jersey integration I need to be able
to pass it an existing instance created by warp-persist.
PS: I'm not happy with my own implementation either. It's simply not
clear when Guice versus Jersey should be injecting objects. I don't
think this will be solved until Guice can import Jersey bindings.
Gili
Sundar wrote:
> For people looking for Jersey and Guice integration,
>
> Jersey and Guice adapter availabe as part of google code.
>
> http://code.google.com/p/jerseyguice/
>
> -Sundar
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
