[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Remoting and remote classloading

[ron.sigal@jboss.com]

"scott.stark at jboss.org" wrote : 
  | A potential problem I see with the MarshallerLoaderHandler is that is calling the ServerInvoker for a class loader.
  | 

Right, pre-JBREM-962, that's all it did, which restricted the facility to Remoting's classloader.  Now, if that doesn't work, it will try all the configured classloader repositories.  E.g., if the Connector MBean is configured like


  |    <mbean code="org.jboss.remoting.transport.Connector"
  |           name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
  |       <depends>jboss.aop:service=AspectDeployer</depends>
  |       <attribute name="Configuration">
  |          <config>
  |             ...
  |             
  |             <repositories>
  |                <repository>jboss.remoting:loader=titan1.ear</repository>
  |                <repository>jboss.remoting:loader=titan2.ear</repository>
  |             </repositories>
  |             
  |             ...
  |          </config>
  |       </attribute>
  |    </mbean>
  | 

where, for example, jboss.remoting:loader=titan1.ear comes from 


  | <jboss-app> 
  |     <loader-repository>jboss.remoting:loader=titan1.ear</loader-repository>
  | </jboss-app>
  | 

then MarshallerLoaderHandler will also try jboss.remoting:loader=titan1.ear and jboss.remoting:loader=titan2.ear.

What I'd like to do is replace the "repositories" element with a list of classloaders.

"scott.stark at jboss.org" wrote : 
  | Yes, if we can have an application level bean register its class loader with the remoting layer to enable remote class loading, that is what we want. 
  | 

I was thinking more in terms of declarative injection by way of *-beans.xml files.  I'm not sure I see how an application level bean would get access to Remoting ... .  Actually, that raises a question I've been meaning to figure out: What is the microcontainter/POJO analog to grabbing an MBeanServer and accessing an MBean by way of its object name?

"scott.stark at jboss.org" wrote : 
  | if we can have an application level bean register its class loader ...  Registering a class loader with remoting should be a priviledged operation with a security check to ensure only application framework code can perform the registration.
  | 

I'm missing something.  If "application framework code" means the Application Server, then these statements sound contradictory ... .  Also, is there a way for a Connector method to check that it's being called by JBoss code?

"scott.stark at jboss.org" wrote : 
  | simply a feature, not a crippling issue in my view.
  | 

I won't let this hold up the 2.4.0.SP1 release unnecessarily.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169409#4169409

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169409