As Pax-Logging use a ManageService, you may have an issue with the
configuration loading.
Once again, I think it's not correct to import pax-logging: it's not the
purpose of pax-logging to provide a logging facility itself, the purpose
is to provide multiple logging framework in a central way.
That's why, it's better in the bundles to define the logging system to
use without version. For instance, it's what we use in Karaf and Cellar
itself: we import slf4j (not pax-logging).
Regards
JB
On 12/28/2012 04:25 PM, raman99_m wrote:
We put pax-logging as provider in manifest to make sure pax-logging is picked
up instead of any other log4j deployed in container. As we use Karaf as a
container, there is a possibility that others may deploy log4j into
container.
If we update etc/startup.properties with two versions of pax-logging bundles
how pax-logging.cfg is shared? We tried that option seems logging is not
working. I can verify again.
Regards
Raman
--
View this message in context:
http://karaf.922171.n3.nabble.com/can-we-run-two-version-of-pax-logging-in-Karaf-tp4027150p4027154.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
