edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (EDGENT-206) Allow new applications to be registered with new code.
Date Tue, 28 Feb 2017 21:37:45 GMT

     [ https://issues.apache.org/jira/browse/EDGENT-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dale LaBossiere resolved EDGENT-206.
    Resolution: Fixed

was resolved a long time ago via https://github.com/apache/incubator-edgent/pull/149

> Allow new applications to be registered with new code.
> ------------------------------------------------------
>                 Key: EDGENT-206
>                 URL: https://issues.apache.org/jira/browse/EDGENT-206
>             Project: Edgent
>          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

View raw message