[
https://issues.apache.org/jira/browse/RIVER-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908727#comment-13908727
]
Dennis Reedy commented on RIVER-435:
------------------------------------
I'm not sure what the real consequences are if a classloader that loads service
implementation classes and then is a parent to a classloader then then is used
to load either a discovered service (or receives a remote object as a
parameter) is.
There will be another classloader created by underlying RMI infrastructure to
load the class (since the service classloader) will not have the other
service's proxy classes in it's search path). I may be missing something, but
what are the issues here?
> 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)
