[
https://issues.apache.org/jira/browse/TAMAYA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anatole Tresch updated TAMAYA-148:
----------------------------------
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...
was:
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.
> Review & Verify OSGi Support in Tamaya
> --------------------------------------
>
> Key: TAMAYA-148
> URL: https://issues.apache.org/jira/browse/TAMAYA-148
> Project: Tamaya
> Issue Type: Improvement
> Components: OSGi
> Affects Versions: 0.2-incubating
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 0.3-incubating
>
>
> 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...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
