Discussion:
[jira] [Created] (LOG4J2-815) Unify the two JMS appenders into a single appender
Matt Sicker (JIRA)
2014-09-06 04:07:28 UTC
Permalink
Matt Sicker created LOG4J2-815:
----------------------------------

Summary: Unify the two JMS appenders into a single appender
Key: LOG4J2-815
URL: https://issues.apache.org/jira/browse/LOG4J2-815
Project: Log4j 2
Issue Type: Improvement
Components: Appenders
Affects Versions: 2.0.2
Reporter: Matt Sicker
Assignee: Matt Sicker
Fix For: 2.1


The split between JmsQueueAppender and JmsTopicAppender is quite arbitrary, especially since we use JMS 1.1 and not 1.0. These classes should be merged into a single JmsAppender that has plugin aliases for backwards compatibility.

I've already got some progress done toward this in the messaging-module branch. I'm just working on finishing the backwards compatibility and we should be good to go!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Matt Sicker (JIRA)
2014-09-06 04:59:29 UTC
Permalink
[ https://issues.apache.org/jira/browse/LOG4J2-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124314#comment-14124314 ]

Matt Sicker commented on LOG4J2-815:
------------------------------------

Almost complete. Code is merged in master. Still needs a documentation update.
Post by Matt Sicker (JIRA)
Unify the two JMS appenders into a single appender
--------------------------------------------------
Key: LOG4J2-815
URL: https://issues.apache.org/jira/browse/LOG4J2-815
Project: Log4j 2
Issue Type: Improvement
Components: Appenders
Affects Versions: 2.0.2
Reporter: Matt Sicker
Assignee: Matt Sicker
Labels: jms
Fix For: 2.1
The split between JmsQueueAppender and JmsTopicAppender is quite arbitrary, especially since we use JMS 1.1 and not 1.0. These classes should be merged into a single JmsAppender that has plugin aliases for backwards compatibility.
I've already got some progress done toward this in the messaging-module branch. I'm just working on finishing the backwards compatibility and we should be good to go!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Matt Sicker (JIRA)
2014-09-06 05:14:28 UTC
Permalink
[ https://issues.apache.org/jira/browse/LOG4J2-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker resolved LOG4J2-815.
--------------------------------
Resolution: Implemented

Code complete. Will close this issue once all the documentation has been updated.
Post by Matt Sicker (JIRA)
Unify the two JMS appenders into a single appender
--------------------------------------------------
Key: LOG4J2-815
URL: https://issues.apache.org/jira/browse/LOG4J2-815
Project: Log4j 2
Issue Type: Improvement
Components: Appenders
Affects Versions: 2.0.2
Reporter: Matt Sicker
Assignee: Matt Sicker
Labels: jms
Fix For: 2.1
The split between JmsQueueAppender and JmsTopicAppender is quite arbitrary, especially since we use JMS 1.1 and not 1.0. These classes should be merged into a single JmsAppender that has plugin aliases for backwards compatibility.
I've already got some progress done toward this in the messaging-module branch. I'm just working on finishing the backwards compatibility and we should be good to go!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Matt Sicker (JIRA)
2014-09-21 17:27:33 UTC
Permalink
[ https://issues.apache.org/jira/browse/LOG4J2-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker closed LOG4J2-815.
------------------------------

Manual updated.
Post by Matt Sicker (JIRA)
Unify the two JMS appenders into a single appender
--------------------------------------------------
Key: LOG4J2-815
URL: https://issues.apache.org/jira/browse/LOG4J2-815
Project: Log4j 2
Issue Type: Improvement
Components: Appenders
Affects Versions: 2.0.2
Reporter: Matt Sicker
Assignee: Matt Sicker
Labels: jms
Fix For: 2.1
The split between JmsQueueAppender and JmsTopicAppender is quite arbitrary, especially since we use JMS 1.1 and not 1.0. These classes should be merged into a single JmsAppender that has plugin aliases for backwards compatibility.
I've already got some progress done toward this in the messaging-module branch. I'm just working on finishing the backwards compatibility and we should be good to go!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Loading...