Re: Yoko and java.endorsed.dirs question

[Donald Woods]

I'm actually seeing a failure to start the server on certain IBM JVM's, like the IBM SDK for Solaris (or HP-UX.) This is due to a unique packaging change, where they supply a jre/lib/endorsed directory which contains the following -

  ibmcertpathfw.jar        ibmjgssfw.jar            ibmpkcs.jar
  ibmcertpathprovider.jar  ibmjgssprovider.jar      ibmsaslfw.jar
  ibmcfw.jar               ibmjmxstubsties.jar      xml.jar
  ibmext.jar               ibmorb.jar
  ibmjcefw.jar             ibmorbapi.jar






-Donald

Rick McGuire wrote:

For Linux, Windows and AIX, there is no jre/lib/endorsed directory, which matches the layout of the Sun JDK for Linux, Windows and Solaris. So, due to the above JDK, don't we need the Geronimo lib/endorsed directory before the JDK's?

Donald Woods wrote:

What order should the paths be for java.endorsed.dirs?
Should it be -
1) JDK's lib/endorsed before Geronimo's lib/endorsed
2) Geronimo's lib/endorsed before the JDK's lib/endorsed


  "Incorrect level of org.omg.CORBA classes found.
   Likely cause is an incorrect java.endorsed.dirs configuration"

I'm wondering due to the following warning/exception in the geronimo-corba module - Don't we need the Yoko implementation in the endorsed classpath before the JDK's implementation???

For the yoko code, I'm not sure it matters. The classes the yoko code overrides is contained in the base JVM, not in jar files contained in the endorsed dirs. Not including the yoko jars in the endorsed dirs is one potential cause of that error (and a frequent one for 2.0 until the CORBA support was fully enabled). There are other situations as well that can lead to that. Are you encountering the error, or just wondering because you saw the message in the yoko code?

Rick

-Donald

smime.p7s
Description: S/MIME Cryptographic Signature