It will not really help you, if required bug fixes have not been implemented
yet. BTW, I gave suggestions, but I believe no one was interested in.
Package-resolution in OSGi is the main problem because it is very time
consuming. You should start with modularizing the deployment. E.G. make
Appender bundles so that costumers can decide which functionality they want
to use. This reduces the dependencies, because you don't have to start
unused but dependent bundles. The second approach is to embed transitiv
dependencies. But this is bad practise. Log4j2 has many Javax dependencies.
Such dependencies should be avoided. The usual suspects....

But don't worry. Logback is not better. Logback uses the groovy library
which is about 5MB in size. In comparison, my OSGi container inclusive of
all bundles is 2.2 MB in size.

Most logger systems have the same problem, they are too large and
unmanageable. Little test capability is also a problem that goes along with
large logger systems.

It surprises me again and again that it still does not exist a modular and
interchangeable lightweight logging system today. Even OSGi has no
well-designed logging-interface in my opinion. OSGi pretends you to
implement a LogService. This service is not part of the core, but a part of
a LogService-bundle that must be started after the framework. Error messages
of the framework can be lost. The Apache Felix implementation uses an
internal logger, but if you adapt it for your own needs you have to link
against the OSGi implementation but not against the OSGi interface, which is
bad practise. Last Friday I had a discussion with my superior and we ended
with the question whether it makes sense to write our own lightweight
interchangeable logger implementation.



--
View this message in context: 
http://apache-logging.6191.n7.nabble.com/log4j-2-official-release-date-tp40916p40951.html
Sent from the Log4j - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to