Same would probably work w/ EAServer, the Sybase app server, it (in violation no doubt) allows IO access also. I guess the IO restrictions are to allow for distribution/failover/loadbalancing --- where the file system could "change under you" as your EJB is run on another host --- but app server folks appear to be saying "if you want to, your call..."
regards Adam -----Original Message----- From: Bobby Nations [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 4:57 PM To: Log4J Users List Subject: Re: Using log4j with EJB Scot, We're using WebLogic 6.1 and having no trouble with the configureAndWatch( "log4j.properties" ) methods. We placed the directory holding the properties file into the server's classpath, and it finds it no problem. Yeah, I know, this violates the EJB spec, but hey, it works for us and we have no plans of switching app servers any time soon. Of course, BEA could always take it away from us at some point, but we'll cross that bridge when we get to it. Your mileage may vary, Bobby Bellamy, Scot wrote: >In our environment we are using J2EE, including EJB. We would like to >employ Log4J as our logging utility for new projects. This isn't a >problem with the exception of EJB. We have identified a way to write >log messages utilizing JMS to send to a separate running process. >However, 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? > > > >Thanks, > >Scot. > > > > -- Sr. Programmer / Analyst FedEx Services 20 FedEx Parkway Collierville, TN 38017 (901) 263-6517 -- 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]>
