RMI Classloading problem.... help appreciated.

2008-10-03 Thread David Jencks
I've run into a RMI classloading problem that I don't know how to solve and I'm hoping someone has a suggestion about how to proceed. In this scenario there are 3 jvms: A. gshell B. a controller server C. a cluster node. In B, there are 2 classloaders of interest: j2ee-security and plugin

Re: RMI Classloading problem.... help appreciated.

2008-10-03 Thread Rick McGuire
occurring in the same place in the FarmBean code? If not, are there any fundamental differences between the call environments? Rick David Jencks wrote: I've run into a RMI classloading problem that I don't know how to solve and I'm hoping someone has a suggestion about how to proceed

Re: rmi classloading exceptions when launching 1.1

2006-04-26 Thread Sachin Patel
Shoot, I was hoping a stand-alone test case would fail as well, but it doesn't. :( So the issue is specific to invoking this within eclipse bundles. - sachin On Apr 25, 2006, at 11:17 PM, Sachin Patel wrote: I'm running into the following exception when launching 1.1 within eclipse

Re: rmi classloading exceptions when launching 1.1

2006-04-26 Thread Sachin Patel
Ok playing around I think I figured out the problem, but its going to be tricky getting a correct solution. The issue is the following... I'm supporting both V1 and V11 there are several jars at the same versions between 1.0 and 1.1 namely (mx4j, commons-logging, spec jars, etc..). Now

Re: rmi classloading exceptions when launching 1.1

2006-04-26 Thread Sachin Patel
At worst case adding duplicate jars with increase the size 1-1.5 megs. Thank you for listening to my conversation with myself :) - sachin On Apr 26, 2006, at 10:05 AM, Sachin Patel wrote: Ok playing around I think I figured out the problem, but its going to be tricky getting a correct

Re: RMI classloading

2005-03-20 Thread Mark
The nested exception case is interesting since there is value in recreating an exception on the client side. From what I recall, Corba does not have a standard way a sending back an arbitrary server exception to the client. As for remote interfaces, the client should already be able to access

Re: RMI classloading

2005-03-19 Thread Dain Sundstrom
On Mar 17, 2005, at 6:06 PM, Alan D. Cabrera wrote: [EMAIL PROTECTED] wrote: Hi, I would like to know if it would be helpful to have a RMI class server. Currently, I see two potential usage: * deployment: currently, we need to be carefull about the exceptions nested within DeploymentException

Re: RMI classloading

2005-03-19 Thread Jeremy Boynes
IIOP has special hooks to do remote class loading javax.rmi.CORBA.Util, which in OpenEJB delegates to org.openejb.corba.util.UtilDelegateImpl. I think we should start with the most basic as RMI classloading is built into the VM and that is what we are using by default for JMX remoting. I think

Re: RMI classloading

2005-03-19 Thread Jeremy Boynes
, which in OpenEJB delegates to org.openejb.corba.util.UtilDelegateImpl. I think we should start with the most basic as RMI classloading is built into the VM and that is what we are using by default for JMX remoting. Everything else would add additional dependencies on the client. That's

RMI classloading

2005-03-18 Thread gianny . damour
Hi, I would like to know if it would be helpful to have a RMI class server. Currently, I see two potential usage: * deployment: currently, we need to be carefull about the exceptions nested within DeploymentException otherwise we will get a ClassNotFoundException. As a matter of fact, by

Re: RMI classloading

2005-03-18 Thread Alan D. Cabrera
[EMAIL PROTECTED] wrote: Hi, I would like to know if it would be helpful to have a RMI class server. Currently, I see two potential usage: * deployment: currently, we need to be carefull about the exceptions nested within DeploymentException otherwise we will get a ClassNotFoundException. As a

RE: RMI classloading

2005-03-18 Thread Bordet, Simone
Hi, Hi, I would like to know if it would be helpful to have a RMI class server. Currently, I see two potential usage: * deployment: currently, we need to be carefull about the exceptions nested within DeploymentException otherwise we will get a ClassNotFoundException. As a matter