Hi
Are there any plans to implement full JMX 1.1 compatibility into Log4J ?
The issue arises from non-compliant Java identifiers. Here is an article
(and sample patch):
http://www.geocrawler.com/mail/msg.php3?msg_id=10504037
As far as I can tell the latest alpha does not fix this issue:
http://
Hi Sam
We are trying to implement full JMX1.1 compatibility as well as to
achieve production quality for the log4j-jmx-extension.
Unfortunately, we can not focus exclusively on this task..however, we
hope to be able to provide first results this month.
Peter
Finch, Sam wrote:
Hi
Are there an
First off, I want to thank you for the response and direction.
Here are the files that I think you need.
- jnisyslog.tar.gz contain the java file and the C file. Inside this file there is also a test directory, which contains a test program and .lcf file that is called by the test.jnisyslog tar
one more point to note.
jnisyslog.tar.gz should be extracted to the logging-log4j/src/java/org/apache/log4j directory. :)
---Original Message---
> From: log4jdev <[EMAIL PROTECTED]>
> Subject: Re: Re: Prototype written : JNI Syslog appender
> Sent: 01 Mar 2004 17:25:57
Don't forget the Bugzilla entry otherwise this email will get lost! :)
Thanks,
Paul
On Tue, 2004-03-02 at 04:25, log4jdev wrote:
> First off, I want to thank you for the response and direction.
>
> Here are the files that I think you need.
> - jnisyslog.tar.gz contain the java file and the C
sdeboy 2004/03/01 23:38:20
Modified:src/java/org/apache/log4j/varia
LogFilePatternReceiverBeanInfo.java
LogFilePatternReceiver.java
Log:
Added a default timestamp format and a 'name' beaninfo entry
Revision ChangesPath
1.3
