[
https://issues.apache.org/jira/browse/LOG4J2-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390803#comment-15390803
]
Gary Gregory commented on LOG4J2-701:
-------------------------------------
Since Apache QPid has a JMS provider
(https://qpid.apache.org/components/jms/index.html), a user could just use our
JMS support plus Qpid to get AMQP.
Or is there a significant benefit to "native" (non-JMS) AMQP support?
It seems reasonable to add of course but we can get there from here already ;-)
Gary
> Add AMQP logging support similar to JMS logging support.
> --------------------------------------------------------
>
> Key: LOG4J2-701
> URL: https://issues.apache.org/jira/browse/LOG4J2-701
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Receivers
> Affects Versions: 2.0
> Environment: Apache Qpid, Apache Apollo 1.x, Apache ActiveMQ 5.x
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Priority: Minor
> Labels: amqp, apollo, qpid
>
> Being able to produce and consume log messages over JMS is a neat feature
> that could be fleshed out a bit more. One step toward accomplishing that
> would be to add more MOM protocols. AMQP is one of the leading standards for
> cross-platform messaging, and the Qpid project provides some nice libraries
> for working with AMQP in general. See the [Qpid Proton
> project|http://qpid.apache.org/proton/index.html] for more details on that.
> I'd like to take this feature as a way to make the JMS appenders and JMS
> receivers (i.e., LogEventListeners) a bit more messaging agnostic. It can
> also pave the way toward supporting a couple other common messaging protocols
> that could be useful (like MQTT and STOMP).
> Ideally, I'd like to have this feature without any Spring libraries as this
> is not a very advanced messaging application feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
