The document from SUN is clear, it just does not work under the Windows platform. It may be fixed in the beta JDK but I have not tried it yet. The problem I can see with the current solutions is the requirement for the system variable, java.endorsed.dirs, to be defined. In some environments, this can be a hard / error prone process. I.e. Some products have .exe based launchers that you would have to dig through config files to determine where the java startup line is stored, or Tomcat where I would have to modify the production startup file to include the new variable.
My $.02 John G Shane Curcuru wrote: > > IMHO, SUN should create the endorsed directory as part of the > > installation and fill it with the "endorsed jars". Replacement would > then > > be a snap. rt.jar would remain to be the sun.* and java.* packages. > > On one hand, I agree that this would be a stunningly useful idea as > well! On the other hand, allowing users to (possibly by mistake) > overwrite part of the shipped JDK install is a bad idea. But it would > have been nice if they had included clear doc as to how and where the > various endorsed standards impls were packaged and why, instead of > lumping the single rt.jar file together. > > Hmmm - I wonder how other JDK vendors will package this stuff? 8-) > > ===== > - Shane > > <eof .sig="'When I use a word,' Humpty Dumpty said, > in a very scornful tone, 'it means just what I > choose it to mean - neither more nor less'" > "Oohayu oyod?!"=gis. /> > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - Feel better, live better > http://health.yahoo.com -- -------------------------------------- John Gentilin Eye Catching Solutions Inc. 18314 Carlwyn Drive Castro Valley CA 94546 Contact Info [EMAIL PROTECTED] Ca Office 1-510-881-4821 NJ Office 1-732-422-4917
