Ceki,
Both Michael and I have expressed an interest in maintaining the
JMSAppender/JMSReceiver pair.
What are we to do next?
Mark
On Fri, 18 Feb 2005 19:45:40 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote:
>
> Michael, Mark (van der Voort),
>
> Do you have an interest in maintaining the JMSApp
Yes, I'm also
willing to help maintain a JMSAppender/JMSReceiver pair with the added
capability.
Michael
Los
smime.p7s
Description: S/MIME cryptographic signature
Sure,
I wrote it for incompany use so I'll have to maintain it anyway.
Better a general version than a proprietary one.
Mark van der Voort
On Fri, 18 Feb 2005 19:45:40 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote:
>
> Michael, Mark (van der Voort),
>
> Do you have an interest in maintaining the
Michael, Mark (van der Voort),
Do you have an interest in maintaining the JMSAppender/JMSReceiver pair?
At 09:39 AM 2/16/2005, Mark van der Voort wrote:
I've created a JMSAppender as Michael stated, and a matching JMSReceiver.
The extension boils down to adding an optional layout to the
JMSAppender
I've created a JMSAppender as Michael stated, and a matching JMSReceiver.
The extension boils down to adding an optional layout to the
JMSAppender, and a decoder to the JMSReceiver. I personally use the
standard XMLLayout and XMLDecoder.
I can upload or include the files, what is standard procedur
Hi Michael,
Thank you for the contribution. However, I do not think it is suitable go
into log4j proper. If another log4j committer is interested in placing it
in log4j-sandbox and take responsibility for maintaining it, he is most
welcome to do so.
In the mean time, my recommendation would be
Please consider adding the capability to publish a text message via JMS.
When trying out the new Chainsaw, I was getting StreamCorruptedException.
I believe this was due to incompatible LoggingEvent serializations between
versions 1.2.x and 1.3
The event producer was using log4j 1.2.8. Chainsaw
