You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/23 23:20:16 UTC

[jira] [Commented] (QUARKS-206) Allow new applications to be registered with new code.

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

ASF GitHub Bot commented on QUARKS-206:
---------------------------------------

GitHub user ddebrunner opened a pull request:

    https://github.com/apache/incubator-quarks/pull/149

    [WIP] QUARKS-206 Initial api to add a jar containing applications

    

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

    $ git pull https://github.com/ddebrunner/incubator-quarks quarks-206

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

    https://github.com/apache/incubator-quarks/pull/149.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 #149
    
----
commit f91be48c87761fcbd0c719acfedcef06738c2807
Author: Daniel J. Debrunner <de...@us.ibm.com>
Date:   2016-06-23T23:19:28Z

    QUARKS-206 Initial api to add a jar containing applications

----


> Allow new applications to be registered with new code.
> ------------------------------------------------------
>
>                 Key: QUARKS-206
>                 URL: https://issues.apache.org/jira/browse/QUARKS-206
>             Project: Quarks
>          Issue Type: New Feature
>          Components: Runtime
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>
> The application service allows registration of applications at any time but the code must already be available to the class loader. This would add the ability to register a new jar using a URI and applications within it.
> Probably two cases the URI is remote and Quarks would fetch the jar and save it locally, or the jar is a file URL that has been installed by some other system.
> Need o think about if just the URL is provided and the list of applications to register is in the jar, e.g. as a service provider, or the list of applications is provided with the jar. Seems making the jar self-contained is the best approach.



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