I have a question regarding the suitability of Log4J for use in EJB applications.
Log4J Category instances are controlled using a Singleton-style approach. All logging calls are synchronized in order to check for runtime configuration changes. In the opinion of several of my colleagues, this violates the EJB programming strictures on manual thread synchronization and use of modifiable static variables. Do you have any comments on this? Do you consider Log4J to be compliant with EJB strictures? Your response is appreciated. Best regards Aaron Knauf Contract Java Developer CAUTION: This correspondence is confidential and intended for the named recipient(s) only. If you are not the named recipient and receive this correspondence in error, you must not copy, distribute or take any action in reliance on it and you should delete it from your system and notify the sender immediately. Thank you. Unless otherwise stated, any views or opinions expressed are solely those of the author and do not represent those of Vodafone New Zealand Limited. Vodafone New Zealand Limited 21 Pitt Street, Private Bag 92161, Auckland, 1020, New Zealand Telephone + 64 9 357 5100 Facsimile + 64 9 377 0962 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
