Jersey Robot

@glassfishrobot Commented cowwoc said: Proposal: 1. Isolate all HK2-specific bindings into reusable "factories". 2. Extract all HK2-specific code into its own module. jersey-core would only use JSR 330 to @Inject...

@glassfishrobot Commented cowwoc said: Can someone please change the title of this issue from "Enable Jersey/Guice integration via HK2 Guice Bridge" to "Guice support"? I don't think we'll be able...

@glassfishrobot Commented jontro said: I would just like to add that I support @cowwoc completely. After a couple of months now since switching to jersey 2.x from the 1.x version...

@glassfishrobot Commented bowenwr said: I'm also voicing my support for moving forward on this issue.

@glassfishrobot Commented djxak said: I think Jersey need to be DI framework agnostic. For example I have a maven module in my application with JPA persistence classes. Entities and DAOs....

@glassfishrobot Commented jitterted said: I've voted for this, but I also wanted to comment that because of this issue alone, I may be forced to switch to another JAX-RS provider...

@glassfishrobot Commented aldenquimby said: @jitterted i was able to get things working by following [this HK2 comment](https://java.net/jira/browse/HK2-121?focusedCommentId=371397&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_371397). It's not great, but should work until the Jersey guys finally get around...

@glassfishrobot Commented sugis said: I too, after many happy years of Jersey use, had to switch to RESTeasy over this issue 

@glassfishrobot Commented natros said: I start to feel you pain over this issue. I have a large code base that dependes on jersey 1.x and can't simple switch to Resteasy.

@glassfishrobot Commented jkidd said: @cowwoc +1 As long as the support for Guice in Jersey 2.x is so cumbersome, I myself will not be willing to switch to Jersey 2\....