May 2015 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1075) Logback can't read project property resource running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1076) Logback can't load custom project appender running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1076) Logback can't load custom project appender running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1075) Logback can't read project property resource running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1074) Undertow web server support
by Eduard Dudar (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-315) support groovy configuration in logback-access
by Eduard Dudar (JIRA) 29 May '15

29 May '15

1 0

JMSQueueAppender and JMSTopicAppender implements many common code
by Ramon Gordillo 27 May '15

27 May '15

Hi. I am extending some classes for JMS logging, and I want to share my thoughts. 1) Queue and Topic Appender share a lot of common code. The only difference is at JMS level (for example, QueueSession and TopicSession). So I wonder if it is possible to implement the common code at parent level (JMSAppenderBase), using common methods (like getter getSession) and override those common methods in the children. Example: Current code (JMSQueueAppender): ObjectMessage msg = queueSession.createObjectMessage(); Serializable so = pst.transform(event); msg.setObject(so); queueSender.send(msg); Proposed code (on JMSAppenderBase): ObjectMessage msg = getSession().createObjectMessage(); Serializable so = pst.transform(event); msg.setObject(so); getSender().send(msg); Proposed code (on JMSQueueAppender): public Session getSession(){ return getQueueSession() } Proposed code (on JMSTopicAppender): public Session getSession(){ return getTopicSession() } and same for getSender(). 2) JMS Serialization can only send ObjectMessage. Following the same approach as encoders, it will be very useful to provide other kind of serialization, like MapMessage, TextMessage + Headers, etc. Currently, I have done exactly this in my project but manually overriding the methods. Configuring the serialization through configuration will be more elegant and extensible. Please, share your thoughts. Regards. Ramon

1 0

[JIRA] (LOGBACK-1073) Use a WatchService for reconfiguration
by Steffen Brüntjen (JIRA) 27 May '15

27 May '15

1 0

[JIRA] (LOGBACK-1066) cannot close files with SiftingAppender
by Enrico Medves (JIRA) 25 May '15

25 May '15

1 0

[JIRA] (LOGBACK-1072) Allow to set ClassLoader on GenericConfigurator
by Alexander Kitaev (JIRA) 24 May '15

24 May '15

1 0