ittle different than the
millsecond value in the timestamp that goes out to the file through the
FileAppender, correct?
- Brendan
-Original Message-
From: CONNER, BRENDAN (SBCSI)
Sent: Tuesday, February 07, 2006 10:28 AM
To: Log4J Users List
Subject: RE: Using Layouts with JMSAppender
.
- Brendan
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 7:12 PM
To: Log4J Users List
Subject: Re: Using Layouts with JMSAppender
the layout in your log4j.properties is irrelevant to JMSAppender,
since it is sending the serialized
? So does our MDB have to have access to our
log4j.properties file and read it manually? I'm hoping I'm missing
something here ;-)
- Brendan
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 6:40 PM
To: Log4J Users List
Subject: Re
and read it manually? I'm hoping I'm missing
something here ;-)
- Brendan
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 6:40 PM
To: Log4J Users List
Subject: Re: Using Layouts with JMSAppender
In your MDB, just have an ins
In your MDB, just have an instance of a Layout and format it then.
Otherwise you don't want to use JMSAppender. JMSAppender is about
sending the binary contents of the LoggingEvent over JMS for some
other reason (say, to view in a GUI, or store in a DB).
Paul
On 07/02/2006, at 11:36 AM, CO
I finally got the JMSAppender working, and I can receive the logged
message using a Message Driven Bean. While working with my example, I
noticed that the message that is received by the onMessage() method is
an instance of ObjectMessage, which wraps an instance of LoggingEvent.
My question is:
H
