Home/ Questions/Q 7607789
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T00:45:15+00:00

We use a mixed OSGi and non-OSGi environment. Therefore all our produced JARs are

  • 0

We use a mixed OSGi and non-OSGi environment.
Therefore all our produced JARs are Bundles, to enable deployment and runtime both inside and outside of the OSGi container. Therefore, all our are written without any OSGi API integration, and we use a single OSGi extender bundle to register all services as OSGi services.

I would like to use a single DI solution (i.e. the same configuration file(s)) when wiring the system together both inside and outside of the OSGi container. This, rather effectively, prevents me from using simple blueprint DI.

What would you recommend here?
Is there any best practices collected for this kind of scenario?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Use Spring.

    It will obviously work outside of OSGi, and you can use Spring dm to adapt it to work inside of OSGi. It simply requires the addition of an osgi context file to bind beans to/from the service registry.

    We have used it in multiple projects for several years for Eclipse RCP apps. It can be used to bind things at the UI level in this particular case as well.

    • 0