river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Rollo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging
Date Mon, 24 Feb 2014 04:08:19 GMT

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

Dan Rollo commented on RIVER-435:
---------------------------------

I'm certain I do not understand all the intricacies of the class loader issues being discussed,
but I can say that having  service interface classes appear in multiple different jars has
always be confusing for me from a developer perspective. If it is not a hinderance to some
important feature, my opinion is putting the "shared"/"common" service interface classes into
a single lib-api jar is far simpler in concept and practice. I think it would very much worth
the effort of creating a new jar. Tracking which classes are duplicated in which jars has
always smelled funny to me.


> 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.1.5#6160)

Mime
View raw message