Hi Michael Thanks for your reply. I've been having similar thoughts, so thanks for confirming them. It's possible that when we tried commons-logging that it wasn't configured properly to use log4j - and hence reverted to using the JDK's logger... causing the same problem.
I'll try using log4j directly, as to mitigate any interference from other logging frameworks. If that works, then I'll try introducing commons-logging again. Thanks for your input. Regards Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CTJUG Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/CTJUG-Forum For the ctjug home page see http://www.ctjug.org.za -~----------~----~----~----~------~----~------~--~---
