On 25/09/2013 9:45 PM, Marshall Pierce wrote:
On 09/25/2013 07:38 AM, Gili wrote:
Hi,

I authored Guice integration for Jersey 1.0 a few years ago but times
have changed and I no longer have as much free time as I used to. Jersey
2.0 is out, with Spring support but Guice support is nowhere in sight:
https://java.net/jira/browse/JERSEY-1950

I tried applying pressure on the Jersey authors but got no response at
all. Is anyone able to help out by picking up this issue and running
with it? For everyone else, I would appreciate your vote for this issue.

Thank you,
Gili

I'm definitely interested in Guice support for Jersey 2. I don't have a lot of free time, but I'm happy to help how I can. The lack of Guice support is one of the few issues preventing me from adopting Jersey 2.

-Marshall

Hi Marshall,


In theory we should be able to leverage javax.inject.Inject to provide a consistent implementation for all compliant injectors. In practice, it's not that simple. The devil in the details is GuiceFilter.

The problem is that HK2 requires us to construct a ServletContainer to get a ServiceLocator, then pass that into the HK2-Guice bridge and get back an Injector. In the flip side, Guice wants us to construct GuiceFilter to get an Injector, and use it to inject ServletContainer. Each framework assumes it comes first. It's not clear how they solved this problem for Spring, but my guess is they don't have the equivalent of GuiceFilter.

When I implemented Guice integration for Jersey 1.0, the first thing I did was examine the Spring implementation. I suggest we begin by doing the same here. I'll try to take a look over the next two days. Please try to do the same on your end.

PS: The lack of Guice support is also one of the few issues preventing me from adopting Jersey 2.

Thanks,
Gili

--
You received this message because you are subscribed to the Google Groups 
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to