river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Trasuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging
Date Fri, 21 Feb 2014 19:15:26 GMT

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

Greg Trasuk commented on RIVER-435:

I think the question was whether the SAR should call out two possible directories to put jars
in (lib, lib-dl) or three (lib, lib-dl, lib-api).  Peter was suggesting that a separate dir
for api jars would allow a better classloader layout.  I was wondering if that could even
be done without changes to the JSK library (it can).  Also, any feature in a spec has an implementation
cost, so I was working through the impact of a classloader layout to figure out if the implementation
would be unnecessarily onerous for implementors.

I'm on the fence here.  I'm perfectly happy with just differentiating on "should this jar
be available to the outside or not?".  At the same time, Peter brings up a good point (although
I don't think that classloader layout has been common practice so far).  If separating out
the API jars is a desirable thing, but the SAR spec only allows for internal and external,
then the SAR spec would be hampering a feature, and you'd have to resort to pattern-matching
in the name, or something else.

So, I don't know.  Differentiating between what is used on the classpath and what is published
on the codebase server is absolutely essential.  Differentiating API jars seems like it might
be a good idea.  Thoughts?

> 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