[
https://issues.apache.org/jira/browse/STREAMS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223537#comment-14223537
]
ASF GitHub Bot commented on STREAMS-234:
----------------------------------------
GitHub user robdouglas opened a pull request:
https://github.com/apache/incubator-streams/pull/145
STREAMS-234 | Added an implementation of the MessagePersister interface ...
...which uses SLF4J to write out JMX information
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robdouglas/incubator-streams STREAMS-234
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/145.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #145
----
commit 8a0b7df44c3b8097119c94f5b0e518bdf17f0027
Author: Robert Douglas <[email protected]>
Date: 2014-11-24T16:20:09Z
STREAMS-234 | Added an implementation of the MessagePersister interface
which uses SLF4J to write out JMX information
----
> Write implementation of JMX Message Persister that uses SLF4J
> -------------------------------------------------------------
>
> Key: STREAMS-234
> URL: https://issues.apache.org/jira/browse/STREAMS-234
> Project: Streams
> Issue Type: Task
> Reporter: Robert Douglas
>
> As a Streams operator, I should be able to persist my JMX bean information
> via SLF4J instead of via HTTP broadcasts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
