Hi Stuart,
The discussion was scattered across multiple threads, but it
more-or-less started here:
https://java.net/projects/jersey/lists/users/archive/2013-11/message/74
(see the bottom of the message)
In short, we need Jersey to code against some portable mechanism so you
can swap in Guice, Spring or HK2 at configuration time but JSR 330
doesn't go this far. CDI 1.x is seen as bloated but the only possible
solution because JSR 330 is not being maintained.
Jersey made the incorrect assumption that they could code directly
against HK2 (a DI implementation) and it would "bridge" calls to
Guice/Spring/etc at runtime. In practice, Guice/Spring/etc don't provide
the necessary functionality to co-exist with another DI framework (e.g.
delegating injection). I'd like JSR 330 to be extended so that users may
use at most one DI at a time, but the actual implementation be chosen at
runtime.
The remaining alternative is to add injection delegation into Guice and
Spring, in which we'd be able to run multiple DIs at runtime. We don't
really need this if JSR 330 is fixed, but this might be quicker to
implement (less bureaucracy).
Gili
On 02/12/2013 3:19 PM, Stuart McCulloch wrote:
On 2 Dec 2013, at 19:28, Gili <[email protected]> wrote:
Hi,
Do the Guice authors plan to extend JSR 330 in the near future? If not, are you
willing to relinquish control of this JSR to others who have expressed a
willingness to do so? The teams behind Jersey, HK2 and Glassfish have expressed
a willingness to pick up this ball.
Sounds interesting, is there a link to the Jersey/HK2/GlassFish discussion?
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.
