Hi Gary,
It is best practise to provide an implementation within a separate bundle
whereas the interface is provided by an other bundle. You can update or
replace the implementation at runtime without stopping the interface bundle.
This is called hot update. But there are some reasons why an
All this hotness is cute but for log4j I predict nothing but trouble
if you try and mix versions of different log4j bundles. I can't
imagine trying to support anything but a simple use the same version
for all log4j bundles scenario.
Gary
On Sep 27, 2013, at 3:53, Roland w...@ids.de wrote:
Hi
You can define the version of the host to which the fragment has to bind to.
So you can have different versions in the osgi container without any
conflicts.
--
View this message in context:
hello Ralph,
...and what about the classloader and package export issues in OSGi
containers? Is there a schedule for a fix?
Regards
Roland.
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/ANNOUNCEMENT-Apache-Log4j-2-0-beta9-released-tp40819p40901.html
Sent from the
On Thu, Sep 26, 2013 at 10:01 AM, Roland w...@ids.de wrote:
hello Ralph,
...and what about the classloader and package export issues in OSGi
containers? Is there a schedule for a fix?
The idea is that we cleared the decks of a _lot_ of bug fixes and some
features for beta9. Now that we've
The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta9 release!
Apache log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x,
and provides
many of the improvements
