Good News

[Anatole Tresch <at...@gmail.com>]

Hi Guys

despite the other things there are also good news: Tamaya's OSGI
integration is working and proven to work in Apache Karaf. This is
definitively a major step. I had to extend a few things to make it work,
but overall things are now almost compatible and behaving similarly.

One big difference to keep in mind is the dynamic behaviour of OSGI. As
long asa  bundle is not loaded the corresponding resources are not visible.
On the other hand bundles that were unloaded disappear similarly. This is
quite different to the static classpath resource location behaviour in SE.
As a consequence the concept of PropertySourceProvider does not match well,
since it's sources are read once, typically during an early loading phase
and not all resources may be visible. What works is to wrap the
PropertySourceProvider into a PropertySource, which is registered and can
reevaluate its property sources whenever accessed or regularly (hence
honoring the current visibility of resources). To make that work I also
extended the ServiceContext (SPI), with two methods for reading resources,
since normal loading via Classloader does not work in OSGI.

I will extend the test suite also for other containers such as Felix,
Equinox etc. to proof it's compatibility and add corresponding module
documentation.

Unfortunately the built seem to struggle with severe issues because
deployment of snapshot artifacts is broken. Hopefully this can be fixed
soon.

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*

Re: Good News

[Werner Keil <we...@gmail.com>]

Something for the new year;-)



Werner


On Fri, Dec 23, 2016 at 9:01 AM, Anatole Tresch <at...@gmail.com> wrote:

> Hi Guys
>
> despite the other things there are also good news: Tamaya's OSGI
> integration is working and proven to work in Apache Karaf. This is
> definitively a major step. I had to extend a few things to make it work,
> but overall things are now almost compatible and behaving similarly.
>
> One big difference to keep in mind is the dynamic behaviour of OSGI. As
> long asa  bundle is not loaded the corresponding resources are not visible.
> On the other hand bundles that were unloaded disappear similarly. This is
> quite different to the static classpath resource location behaviour in SE.
> As a consequence the concept of PropertySourceProvider does not match well,
> since it's sources are read once, typically during an early loading phase
> and not all resources may be visible. What works is to wrap the
> PropertySourceProvider into a PropertySource, which is registered and can
> reevaluate its property sources whenever accessed or regularly (hence
> honoring the current visibility of resources). To make that work I also
> extended the ServiceContext (SPI), with two methods for reading resources,
> since normal loading via Classloader does not work in OSGI.
>
> I will extend the test suite also for other containers such as Felix,
> Equinox etc. to proof it's compatibility and add corresponding module
> documentation.
>
> Unfortunately the built seem to struggle with severe issues because
> deployment of snapshot artifacts is broken. Hopefully this can be fixed
> soon.
>
> 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*
>