river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Reedy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging
Date Thu, 20 Feb 2014 14:39:19 GMT

    [ https://issues.apache.org/jira/browse/RIVER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907003#comment-13907003

Dennis Reedy commented on RIVER-435:

One use case for sharing jsk-lib would be to provide for pooling of discovery management resources.
I have found that the overhead of creating multiple SDMs and discovery management instances
to really be a drain. All of this is implementation specific though, and is moot for the SAR.

A couple of quick thoughts:

* Why the properties file? Seems as if this would be service specific, and I'm not sure what
could not be put into a service' configuration.
* A service's configuration may be the .config or it could be .groovy (or other language)
as long as it provides net.jini.config.Configuration right? Would a container need to know
what the configuration requires (loadable by ConfigurationProvider)
* Do we need some manifest entries to define version of the SAR, any other meta-data?

> Proposed Standard for Single-Archive Service Deployment Packaging
> -----------------------------------------------------------------
>                 Key: RIVER-435
>                 URL: https://issues.apache.org/jira/browse/RIVER-435
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_start
>            Reporter: Greg Trasuk
>         Attachments: SingleArchiveServiceDeployment.docx, SingleArchiveServiceDeployment.pdf
> The attached document proposes the layout and general requirements for an archive file
to support simplified "drag-and-drop" deployment for services that adhere to the Service Starter

This message was sent by Atlassian JIRA

View raw message