Skip to Content.
Sympa Menu

mace-opensaml-users - DOM 3 and Java Web Start

Subject: OpenSAML user discussion

List archive

DOM 3 and Java Web Start


Chronological Thread 
  • From: mochamaster <>
  • To:
  • Subject: DOM 3 and Java Web Start
  • Date: Thu, 5 Feb 2004 19:19:31 -0800 (PST)


OpenSAML requires the use of DOM3 APIs that take
priority over the DOM2 APIs bundled with Java 1.4's
rt.jar. I fully understand the endorsed override
mechanism (place updated APIs in jre/lib/endorsed
directory to override rt.jar). This works fine but my
application is a remotely launched java web start
application. That is, it is downloaded onto the client
by JWS (bundled with Java 1.4) along with dependent
libraries, including DOM3 APIs.

The client requirement is to not install any
additional Java libraries except those that come with
Java 1.4. We don't want to ask each of about 1100
users to install something they have no clue about.
Hence, additional libraries are downloaed with the
main web start application.

I've tried in vain to get the JRE used by web start to
use the downloaded DOM3 APIs in an "endorsed override"
mode. Setting java.endorsed.dirs doesn't work, even
when I specify the location of the DOM3 APIs in the
client's web start cache directory. I've performed the
setting both in code and the application's jnlp file.

Has anyone gotten around this problem by using a
custom classloader? And if there is a classloader
solution, how would one write one such that it
prevents its parent from checking for the class first
(in rt.jar) before delegating to the custom class
loader?

Stalin.

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html



Archive powered by MHonArc 2.6.16.

Top of Page