[jboss-jira] [JBoss JIRA] Commented: (JBAS-3658) Remote classloading service - Redesign

[Tom Elrod (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3658?page=comments#action_12353115 ] 
            
Tom  Elrod commented on JBAS-3658:
----------------------------------

I think I can make the DynLoadingUnitTestCase work using jboss remoting classloading (JBAS-4018) when using unified invoker, but I don't think I can come up with a complete refactor of generic remote classloading based on deployments.  So in short, don't think there is any way I can close this issue within next few days.

Was really hoping this could be discussed more on the forum so know what is really needed (i.e. classloading for ejb clients or any client, if should be generic service, what's wrong with current WebService, how to tie to specific deployments, etc.)

> Remote classloading service - Redesign
> --------------------------------------
>
>                 Key: JBAS-3658
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3658
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>            Reporter: Dimitris Andreadis
>         Assigned To: Tom  Elrod
>            Priority: Critical
>             Fix For: JBossAS-4.2.0.CR1
>
>
> 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