"bstansberry(a)jboss.com" wrote : Just an FYI in case relevant: the AS uses a
forked version of commons-logging, particularly the Log4jLogger class. And, at least for a
portion of startup, JBossTS programatically sets the default implementation of the
commons-logging Log interface, setting it to
com.arjuna.common.internal.util.logging.jakarta.Log4JLogger.
|
| A thread where some issues related to that were discussed:
|
|
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=129207
|
Ugh. I remember this problem, but I didn't remember that the solution was such crap.
Well, one good thing about the MC is that we can just give JBossTS its own commons-logging
instance. That might just be the solution - isolate it and let it do its own thing.
I'll look more once I get closer to completing the integration...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210812#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...