Home/ Questions/Q 7784411
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T20:05:27+00:00

What’s the current situation with integrating Guice and OSGi? I.e. exposing OSGi services from

  • 0

What’s the current situation with integrating Guice and OSGi? I.e. exposing OSGi services from Guice, injecting them, etc.

Peaberry’s main page mentions “The Guice trunk (which will become 2.0)”, but 1.2 seems up-to-date, since it fixes http://code.google.com/p/peaberry/issues/detail?id=58. Its author has switched Sisu, but it doesn’t seem to be released yet. Any others?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The integration of Guice 3.0 and Peaberry 1.2 currently is working like expected. Just the page seems to be a little outdated sind the snippet mentioned above refers to the Guice 2.0 trunk which has been superseded.

    The Bug your referencing is fixed for the 1.2 Peaberry release when you look at the repository history here.

    It’s true that Sisu is currently developed and it solves (at least how I interpret it) some additional problems that are currently existing with Guice + Peaberry + OSGi (e.g. automatic component scanning and discovery) but it isn’t ready yet.

    In my opinion Peaberry solves the same integration cases of DI and OSGi that are also solved by Spring Dynamic Modules (now Eclipse Gemini Blueprint) and is therefore very useful. Also I don’t think necessarily that the Peaberry project will be abandoned in favor of sisu.

    If all you stay true to the OSGi idea of developing independent bundles that are wired through services but you want to use DI inside them, Peaberry currently offers everything you need for that.

    The only problem I’m currently facing with that combination is that the official guice-servlet module doesn’t seem to play with the OSGi HttpService by default.

    • 0