To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-receivers has an issue affecting its community
On 17.09.2011, at 05:19, Ralph Goers wrote:
On Sep 16, 2011, at 5:09 PM, John Vasileff wrote:
On Sep 16, 2011, at 7:41 PM, Joern Huxhorn wrote:
On 16.09.2011, at 19:09, John Vasileff wrote:
On Sep 15, 2011, at 7:46 PM, Ralph Goers wrote:
My gut reaction is that I agree with
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Adding getThrowable() would also reintroduce the issue that such a Message
could not be serialized securely since deserialization would require the
exceptions class on the classpath. In my ParameterizedMessage over at
RFC5424Layout and others use msg instanceof StructuredDataMessage.
StructuredData is a class, but if it were an interface, alternate
implementations of StructuredData could be supported.
One case for this would be if (hypothetically) SLF4J had it's own
SLF4JStructuredDataMessage, and passed
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Adding getThrowable() would also reintroduce the issue that such a Message
could not be serialized securely since deserialization would require the
exceptions class on the classpath. In my
On Sep 17, 2011, at 2:40 PM, Joern Huxhorn wrote:
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Adding getThrowable() would also reintroduce the issue that such a Message
could not be serialized securely since deserialization would
On 17.09.2011, at 21:02, John Vasileff wrote:
On Sep 17, 2011, at 2:40 PM, Joern Huxhorn wrote:
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Adding getThrowable() would also reintroduce the issue that such a Message
could not
On Sep 17, 2011, at 11:40 AM, Joern Huxhorn wrote:
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Adding getThrowable() would also reintroduce the issue that such a Message
could not be serialized securely since deserialization would
On Sep 17, 2011, at 12:26 PM, Joern Huxhorn wrote:
The code simply looks like this:
public void log(Level level, String messagePattern, Object... args) {
if (!isEnabled(level)) return;
ParameterizedMessage message =
ParameterizedMessage.create(messagePattern, args);
On Sep 17, 2011, at 3:26 PM, Joern Huxhorn wrote:
On 17.09.2011, at 21:02, John Vasileff wrote:
On Sep 17, 2011, at 2:40 PM, Joern Huxhorn wrote:
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Adding getThrowable() would also
On 17.09.2011, at 21:34, Ralph Goers wrote:
On Sep 17, 2011, at 12:26 PM, Joern Huxhorn wrote:
The code simply looks like this:
public void log(Level level, String messagePattern, Object... args) {
if (!isEnabled(level)) return;
ParameterizedMessage message =
On 17.09.2011, at 21:26, Ralph Goers wrote:
On Sep 17, 2011, at 11:40 AM, Joern Huxhorn wrote:
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Interesting point on serialization. When would you see serialization
happening? Is
On Sep 17, 2011, at 1:43 PM, Joern Huxhorn wrote:
On 17.09.2011, at 21:26, Ralph Goers wrote:
On Sep 17, 2011, at 11:40 AM, Joern Huxhorn wrote:
On 17.09.2011, at 18:47, John Vasileff wrote:
On Sep 17, 2011, at 8:53 AM, Joern Huxhorn wrote:
Interesting point on
[
https://issues.apache.org/jira/browse/LOG4J2-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-49.
---
Resolution: Fixed
Assignee: Ralph Goers
This really should have been opened as two separate
14 matches
Mail list logo
