Rick, I'm curious about the inherent conflict with the classes that ship with the JVM. Can you explain a little more about what that means (which classes, when and how are they loaded, etc)?
thanks, Paul On 8/11/06, Rick McGuire <[EMAIL PROTECTED]> wrote:
I've run into an interesting snag with getting Geronimo to run with the Yoko ORB. Because there in an inherent conflict with some of the class files that ship with the JVM, it is necessary to prepend the yoko jar file to the bootclasspath when launching the server. This sort of lies outside of the realm of normal execution dependencies. I suppose it can added to the startup batch file, but this means Geronimo can no longer be started by just doing "java server.jar". Additionally, if the Yoko jar is on the bootclasspath, then the Sun version of the ORB adaptor will not function. This is an either/or situation, and the choice, unfortunately, must be made before the JVM is launched. This even comes into play during the build, because there are unit tests for the SunNameService (and also the YokoNameService). Any thoughts on how we should handle this particularly awkward situation? Rick
