Thanks for all of the suggestions that were made to help solve my problem. Open Source rules!
I understand that the EJB container providers are not restricting use of java.io and that is an option. However, I want to keep as close to the specification as possible. The suggestion that Adam made regarding use of JNDI sounds the most appealing and I have a couple of questions: 1. You establish the java:comp/env/... settings for Log4J in the app server XML configuration file(s), correct? 2. Using this method of configuration, are you able to use the automatic reload capability so that changes can be made to the configuration at runtime without having to cycle the app server? 3. The Properties extension you wrote, is that something you would be willing to release to the open source community? :-) (worth a shot). Thanks, Scot. -----Original Message----- From: ajack [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 6:21 PM To: 'Log4J Users List' Subject: RE: Using log4j with EJB "Bellamy, Scot" <[EMAIL PROTECTED]> on 21/03/2002 06:07:55 wrote: [...] we haven't found a good way to utilize the Log4J configuration files in EJB, since EJB code cannot utilize the java.io package. Has anyone discovered a way to accomplish this? We wrote a Properties sub-class that used JNDI to access the java:comp/env/ context, and pass that to PropertyConfigurator.configure(). We also found we could initialise Log4j in an app server start-up function, so EJBs wouldn't have to, and 'cos they shared the VM things worked. You app server may vary. Good luck. regards Adam -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
