On Thu, 18 Apr 2002, Jason Dillon wrote: > I really wish these classes (among others) were not in the core JRE, so > we could simply insist that they use a version that works. Is it > possible that a different version of these classes could be put on the > jboss classpath (in lib/*) for this to work...
There is something along this line that would work. We could have in the system classpath (within our run.jar) a thin wrapper class that fulfills ORBSingleton contract and forwards every invocation to an instance of the actual ORBSingleton class, which it would load with the context CL. I mean: rather than exporting the prop org.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton we export the props org.omg.CORBA.ORBSingletonClass=org.jboss.system.ORBSingleton org.jboss.ORBSingletonDelegate=org.jacorb.orb.ORBSingleton The first prop tells ORB.init() load org.jboss.system.ORBSingleton. This is our thin wrapper class, which is in our run.jar (this way the IBM VM will see it). The second prop is meaningful to the wrapper class only. It specifies the actual ORBSingleton class, which our wrapper should load with the TCL. A wrapper field refers to an actual ORBSingleton instance and is used to forward each wrapper invocation to the actual ORBSingleton. This should be very easy to implement. Kind of a middle ground solution... Rather than exposing the whole pluggable ORB (jacorb.jar) to the system CL, we expose a tiny wrapper class that properly uses the context CL to do what the IBM VM doesn't do for us. Does this make sense? Or I am going way too far just to avoid exposing jacorb.jar to the system CL? Cheers, Francisco _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
