Rick,
I believe what you really want to do is to use the endorsed
directory. This allows you to override the vm implementation of
endorsed specification such as corba (https://java.sun.com/j2se/1.5.0/
docs/guide/standards/index.html). In general, you should try to keep
the stuff in the endorsed jar to a minimum as not to pollute the
class path. In geronimo, to add something to the endorsed dir, you
need to add it to our endorsed manifest entry "Endorsed-Dirs" (I have
no idea where this is set in the build) and you need to modify the
build to put the jar into lib/endorsed by modifying the bin.xml.
-dain
On Aug 11, 2006, at 7:41 AM, Rick McGuire 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
