[jira] [Commented] (NIFI-2716) Allow NiFi to manage embedded JMS Brokers

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562087#comment-15562087 ] 

ASF GitHub Bot commented on NIFI-2716:
--------------------------------------

GitHub user olegz opened a pull request:

    https://github.com/apache/nifi/pull/1118

    NIFI-2716 initial implementation of JMS Broker processor

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/olegz/nifi NIFI-2716

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1118.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 #1118
    
----
commit 146c057b50e6572dee226dded70153a7bedc319f
Author: Oleg Zhurakousky <ol...@suitcase.io>
Date:   2016-09-27T18:14:00Z

    NIFI-2716 initial implementation of JMS Broker processor

----


> Allow NiFi to manage embedded JMS Brokers
> -----------------------------------------
>
>                 Key: NIFI-2716
>                 URL: https://issues.apache.org/jira/browse/NIFI-2716
>             Project: Apache NiFi
>          Issue Type: New Feature
>    Affects Versions: 1.0.0
>            Reporter: Oleg Zhurakousky
>            Assignee: Oleg Zhurakousky
>             Fix For: 1.1.0
>
>
> Several community members expressed interest in NiFi acting as a JMS Broker to avoid deploying and managing external JMS Brokers. While implementing JMS Broker from scratch would be rather complex, using embedded capabilities of some OS JMS Broker implementations (e.g., ActiveMQ) together with native capabilities of  NiFi (i.e., Processor and/or Controller Service) could prove to be a very valuable feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)