[TAMAYA-148] Review & Verify OSGi Support in Tamaya

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 0.2-incubating
• Fix Version/s: 0.3-incubating
• Component/s: OSGi
• Labels: tamaya-clarifying-03 tamaya-wating-response
• Assignee: Anatole Tresch
• Reporter: John D. Ament
• Created: 18/Apr/16 01:06
• Updated: 18/Sep/17 19:34
• Resolved: 22/Dec/16 21:24

Description

Need to verify that Tamaya works in OSGi environments.

The test TestConfigIntegration was used to verify this in the past, but stopped working and was ignored. Its an indication that OSGi support doesn't work too completely.

Functionality Outline:
--------------------------

• Tamaya should load in an OSGI environment correctly. The SE API should work OOTB. This is achieved by loading an alternate ServiceContext implementation, when OSGI is detected (part of the core module). The implementation does explore the bundle for registered ServiceLoader files and registers them as according OSGI services. On the other hand the ServiceContext is retrieving services using the OSGI Service mechanism, ignoring the standard ServiceLoader mechanism (that does not work).
• OSGI services can be leveraged by configuring properties with the Tamaya injection API. Hereby evaluation of the values is performed using the OSGI ConfigAdmin service.
• As third building block Tamaya registers its own ConfigAdmin implementation, with higher priority than the standard one. Tamaya's priority as well if its overriding, or extending the default ConfigAdmin service, is configurable using system properties.

So given we have the first bullet point working, I will definitively also will help writing further tests for these features The basic mechanism I saw working, hopefully there will no bigger surprise...

Issue Links

• is related to: TAMAYA-226 Improve Karaf/OSGi tests in CI