I know and understand that.
Ideally, we may get HK2/Guice integration support soon after Jersey 2.0 is out.
In the long term, I know that CDI 2.0 should bring in a lot of positive changes, in terms of modularising the current CDI into core and extension parts as well as exposing a standard programmatic injection binding APIs. That may be the ultimate solution for problems of having to learn multiple proprietary injection binding APIs.
Marek
On Mar 26, 2013, at 5:23 PM, Gili T. <cowwoc_at_bbs.darktech.org> wrote:
> Speaking strictly for myself, I find it annoying to have to learn and use two different injection frameworks inside my application. It makes the code harder to maintain.
>
> Gili
>
> On Mar 26, 2013 5:21 AM, "Marek Potociar" <marek.potociar_at_oracle.com> wrote:
> Hi,
> unfortunately we do not have any news on Guice support in Jersey 2.0 at the moment. This task is still in the HK2 backlog.
>
> The alternative is to use HK2 injection binding APIs directly, which is what Jersey does internally too (btw. what are the features of Guice that you need?), or to use CDI/Weld that is integrated with HK2 2.1.x and Jersey 2.0.
>
> Marek
>
> On Mar 22, 2013, at 11:27 AM, Jose A. Illescas <jantonio.illescas_at_rbc.com> wrote:
>
> > I see your response about Guice integration via HK2, but this integration it's not done...
> >
> > Exist some alternative? (I really need Guice)
>