ause log4j
violates EJB spec, e.g. reflection, etc)
Thanks.
Mike
-Original Message-
From: ajack [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 10:37 AM
To: 'Log4J Users List'
Subject: RE: Using log4j with EJB
The suggestion that Adam made regarding use of
: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 20, 2002 7:38 PM
>To: Log4J Users List
>Subject:Re: Using log4j with EJB
>
>
>XYZConfigurator.configureAndWatch is known to work (in single server
>mode) with WebSphere 4, Weblogic 6.1, Orion and JBo
n configuration files and databases) and would be
quite dismayed if a container should choose to disallow it.
Rich
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 20, 2002 7:38 PM
To: Log4J Users List
Subject:
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?
Our app server implements JNDI via CORB
:[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
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
XYZConfigurator.configureAndWatch is known to work (in single server
mode) with WebSphere 4, Weblogic 6.1, Orion and JBoss. This particular
method call violates the EJB spec on three accounts. 1) It uses
reflection. 2) It accesses a file. 3) It spawns a thread.
I find the restriction on reflecti
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
"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
I do not use Log4j specifically but if you had an LDAP server you could
store the XML in there. The XML can be quite long depending on the LDAP
server. You would read the string from LDAP and then convert the string to
an InputStream as follows:
byte[] xmlStream = aString.getBytes();
.
-Original Message-
From: Nate Drake [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 20, 2002 2:16 PM
To: Log4J Users List
Subject: RE: Using log4j with EJB
We're using the JDBCAppender by Thomas Fenner
(http://support.klopotek.de/log4j/jdbc/default.htm). This will put you
We're using the JDBCAppender by Thomas Fenner
(http://support.klopotek.de/log4j/jdbc/default.htm). This will put your log
messages into a database. It works great for us.
-Original Message-
From: Bellamy, Scot [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 20, 2002 2:08 PM
To: [EMAIL
12 matches
Mail list logo