[
https://issues.apache.org/jira/browse/RIVER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926166#comment-13926166
]
Greg Trasuk commented on RIVER-435:
-----------------------------------
Consensus seems to be that we don't need to think about classloader hierarchy
in the scope of this spec.
Naming of the jar files ('*-api.jar', '*-proxy.jar', '*-impl.jar', etc) is not
relevant to this spec, insofar as the only thing relevant to the packaging is
whether the jar file should be available as a codebase download or not.
Alternative methods of implementing codebase download are not relevant to this
spec - if an implementation wants to use a method other than the http/httpmd/
codebase annotation, it can arrange to annotate the marshalled classes as
appropriate through the RMIClassLoader mechanism. Again, all that matters for
this spec is whether the jar is available to the outside or not, and that is
indicated by whether the file is placed in the 'lib' or 'lib-dl' folder in the
archive.
The only other thing that seems unresolved is the idea of using artifacts that
are resolvable through an external repository (e.g. Nexus or Artifactory)
rather than putting the jars into the single-archive repository. There are
pluses and minuses, but it seems at least to be outside the scope of this
specification, i.e. Single-Archive Deployment Packaging would seem to be
something different from deployment using an artifact repository. Can I
suggest that a separate specification might be appropriate to cover that?
Could we have comments and final requests for specification changes?
> 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 conventions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
