[jboss-jira] [JBoss JIRA] Closed: (JBAS-2075) Remote classloading service - Redesign

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-2075?page=all ]

Dimitris Andreadis closed JBAS-2075.
------------------------------------

    Fix Version/s:     (was: JBossAS-4.0.5.GA)
       Resolution: Duplicate Issue

Re-opened this subtask as a feature request for the next release.

> Remote classloading service - Redesign
> --------------------------------------
>
>                 Key: JBAS-2075
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2075
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions:  JBossAS-4.0.3RC1
>            Reporter: Adrian Brock
>
> We need to redesign the remote classloading service such that there is more control at the deployment layer
> on what is exposed.
> I will create a forum thread where this can be discussed in more detail.
> Requirement 1:
> Provide sensible defaults, which probably means no remote classloading by default
> Requirement 2:
> Individual deployments can choose whether remote classloading is enabled and what is available remotely
> Requirement 3:
> Allow "aspects" of the deployment to enhance what can be downloaded remotely, e.g. RMI/IIOP generated proxies or
> AOP remoting proxies
> Requirement 4:
> Use the spec defined RMIClassloaderSPI (exposed via an MBean) to make this configurable
> Requirement 5:
> Alternate implementations, e.g. exposure of remote classloading via a servlet in Tomcat or a custom resource url that
> triggers the use of invokers to do remote classloading.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira