In my opinion, the log4j service implementation that JBoss is using is
not "correct". Instead of using Categories for the user data, it is
"pushing" the user data onto the NDC stack. Unfortunately, this means
that if you *DO* use the log4j interface for logging in your code, you
have difficulty formatting your logging messages in a consistent way
with the JBoss logging messages.
I'm actually using a modified version of Log4jService.java for our
purposes that uses Categories for the User data instead of the NDC
stack. Then, in our code, we use Log4j categories pretty readily.
++Jeff
Scott M Stark wrote:
> The main branch has been updated to use the org.apache.log4j framework
> as the default logging implementation. One question is why not adopt the
> log4j framework as the JBoss logging interface as well? I don't see any downside
> to this and there are many benefits. Are there any objections to permitting
> the use of the log4j framework in JBoss/JBossXX code?
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
