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

ASF GitHub Bot commented on NIFIREG-16:
---------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi-registry/pull/9

    NIFIREG-16 Initial Spring integration for nifi-registry-web-api

    This PR converts the nifi-registry-web-api into a Spring Boot project using 
the spring-boot-jersey-starter to integrate Jersey endpoints with Spring's 
context. The nifi-registry-web-api is still packaged and deployed as a war as 
it was before.
    
    In addition, dependencies for spring-core, spring-beans, and spring-context 
were added to the nifi-registry-framework module so that beans/methods can be 
appropriately annotated in the framework. 

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

    $ git pull https://github.com/bbende/nifi-registry spring

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

    https://github.com/apache/nifi-registry/pull/9.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 #9
    
----
commit 8b843ab9fc7674a70d9c150a6b02023586e4a141
Author: Bryan Bende <[email protected]>
Date:   2017-09-06T18:12:22Z

    NIFIREG-16 Initial Spring Boot integration for nifi-registry-web-api

----


> Integrate Spring into the application 
> --------------------------------------
>
>                 Key: NIFIREG-16
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-16
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>
> We should investigate integrating Spring into the application, mainly for 
> dependency injection, taking a similar approach to NiFi with the 
> Jersey-Spring integration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to