I see why you need the special handling. The problem is that it requires
a lot of work on your side.
Perhaps you could describe what you need on the pax logging lists and
issue tracker. If it can be included in pax logging
you could keep the distro as is.
Christian
Am 20.05.2013 10:51, schrieb Iván Zaera Avellón:
Thanks for the pointer, Christian.
I finally managed to make it work, but not configuring PAX. I have removed
pax-web-runtime and pax-web-jetty
from cxf-dosgi-ri-singlebundle-distribution.jar and its MANIFEST. This is
to make CXF load commons logging from my bundle (I have a bundle with
commons-logging) instead of from pax-web-xxx. Then I have introduced a
dependency from my commons-logging bundle to my log4j bundle so that
commons-logging uses log4j. And that's it, because I have an internal
mechanism so that every bundle can configure log4j independently.
I'm getting traces :-).
Regards,
Ivan
2013/5/17 Christian Schneider <[email protected]>
The DOSGi distro should include the pax logging. This should be in charge
of doing the logging. It can be configured using config admin.
See https://ops4j1.jira.com/wiki/display/paxlogging/PaxLogging+inside+PDE
Christian
2013/5/17 Iván Zaera Avellón <[email protected]>
Hi everybody:
I'm new to the list. I have subscribed because I'm trying to use Apache
CXF
in an OSGi RAP application running in Eclipse and I see no way of
activating the logs.
I want to activate the logs because some service I'm exporting is
causing a
NPE inside AEGIS because of a generic type which seems to make it fail. I
have managed to debug everything and see what happens and where the
exception is thrown but I would like to see this kind of errors when I
deploy my app. The WS exportation is done decoupled from the registration
call so there's no way to see if it has failed appart from looking at the
log.
Unfortunately, CXF seems to be using SLF4J which tries to use a
commons-logging LogFactory version bundled inside pax-web-runtime.jar. In
the original pax-web-runtime.jar that class doesn't exists so I cannot
see
its source, but looking at the byte code it seems to have an static field
called m_logFactory which always returns NullLog loggers. Thus, there's
no
way to see nothing in the logs.
Now, the question is: I would like to configure this to dump logs to the
console. How can it be done? Using any system property? Deploying extra
bundles? Placing some magic files in some magic place?
Thanks in advance for your help,
Ivan
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
