You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by Anatole Tresch <at...@gmail.com> on 2017/09/18 15:49:17 UTC
OSGI Support is running !
Dear all
we get closer with OSGI support day by day:
[image: Inline-Bild 1]
Currently we have the following done and running in Karaf (latest version):
- Crucial Tamaya Bundles for OSGI support are all running well.
- OSGI Service Loading (enabled for Tamaya only) is running well. It
also considers bundles loaded later/before etc...
- The integration by default uses the bundles symbolic names as a
configuration prefix. The mapping can be customized by registering an
corresponding SPI as an OSGI service.
- By default Tamaya is updating all configs based on
- an overriding policy
- Manifest entries that allow to enable/disable bundles explicitly
- An overall config to disable or enable Tamaya configuration on
bundles (default=enabled).
- There are Karaf commands implemented (in a separate bundle):
- to access Tamaya configuration.
- to get information on Tamya's configuration and properties.
- to change the Tamaya operation mode/default enabledment as
mentioned above (persisted in the plugin's OSGI configuration).
The output above shows an extract output of the Karaf default config:list
command, where you see that Tamaya successfully adapted the configuration.
Things I still see to be done are:
- *Test* things using component tests
- *Document* it (will do a blog on it)
- Also *update configuration* of bundles loaded or updated (easy but not
yet done).
- Similarly *changes detected on Tamaya's side*, currently are not
updated in OSGI (can be done in a separate bundle as well).
- Test with *other OSGI implementations* as well.
- Currently configuration is adapted based on the operation policy, it
could be event updated. *If Tamaya is removed (or unloaded)*, the
changes are persistent. To support a full rollback/restore, we might store
a history of changes done as well (could be done in the
*TamayaConfigPlugin* configuration as well.
But given that, I would say we have done now a big step forward ;-)
J Anatole
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
*Speaking at:*
[image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]