Rob Walker wrote: > > > > > Sorry to be late in the discussion. The proposed fix may not solve your > > problem starting w/ JDK 1.4.0. The reason is that the code you refer to > > or versions like it are part of the JDK platform and are loaded by the > > bootstrap CL. This means that the current CL will be the bootstrap CL > > and will not see your impl unless it is on the bootstrap classpath. > > Thanks for the response - not sure I follow it though. > > We load the SAX libraries from the Xerces JAR through a custom OSGi > classloader - which is where the problem comes in. We've already used this > approach under JDK 1.4 and it has the same problem and same solutions. So I > don't really understand how 1.4 changes the picture?
Are you saying that you tried your proposed solution on JDK 1.4 and got it to work? I don't know enough about your app to understand. I think we agree that the problem exists in JDK 1.4. In addition, I think that the proposed solution will probably still fail unless you are using JDK 1.4 in a non-standard way. If you have not yet tried it on JDK 1.4, you can try this for yourself by making changes to the FactoryFinder code and placing it in the bootstrap classpath of JDK 1.4. On Sun's JDK, one way is to use the -Xbootclasspath/p option. I would expect that setting the context CL to your custom CL which has access to the impl classes will always work, however. Unfortunately, I have not heard of a better solution to this problem yet. -Edwin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
