I resolved the problem with jul-to-log4j-bridge, only one instruction to code!.
Thanks to all!
mon Laws [simonsl...@googlemail.com]
> Sent: August-20-09 12:33 PM
> To: user@tuscany.apache.org
> Subject: Re: Re: Logging problems with log4j
>
> OK, these are going through the JDK logger. I guess you would need a
> handler that passes the JDK messages off to Log4J. Not sure if this is
> pos
e.org
Subject: Re: Re: Logging problems with log4j
OK, these are going through the JDK logger. I guess you would need a
handler that passes the JDK messages off to Log4J. Not sure if this is
possible as I'm not a expert in this area. Anyone else know? Otherwise
we'll have to do a few Googles
OK, these are going through the JDK logger. I guess you would need a
handler that passes the JDK messages off to Log4J. Not sure if this is
possible as I'm not a expert in this area. Anyone else know? Otherwise
we'll have to do a few Googles to find out if there is one knocking
about.
Regards
Sim
I'm referring to log information like these, for example regarding the
startup of a composite.
[]
20-ago-2009 15.34.51 org.apache.tuscany.sca.node.impl.NodeImpl
INFO: Creating node: engine.composite
20-ago-2009 15.34.51 org.apache.tuscany.sca.node.impl.NodeImpl
INFO: Creating node: engine.co
Hi
It depends what sort of logging you're referring to.
1/ The code tracing type of log statements we have in the code that
are useful for debugging are currently using the JDK logger
2/ The application level errors (the ones that tell you have done
something wrong in your SCA application) are a
