Well I'd have to wholeheartedly agree with that. I don't really understand why Sun did that instead of just letting us put what we want to come first, first in the CLASSPATH. Luckily there was a very specific change, in fact it was completely isolated, so you can get the right stuff out of CVS very easily. That's what I did and just patched the one or two source files that were affected.
Hopefully we'll be getting a 1.2 version soon so this will be a non-issue. =Perry ________________________________________________________________________ This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person. For further information about Epok Inc please see our website at <a href="http://www.epok.net";>http://www.epok.net</a> or refer to the Epok Inc office. -----Original Message----- From: Scott Cantor [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 10:41 AM To: [EMAIL PROTECTED] Subject: RE: R�f. : RE: init problem with jdk1.4.2_05 > Unfortunately this is a hack workaround since the xalan xslt apis are not > part of the actual endorsed override apis. Of course, but the hack is that Sun put these classes into the JDK in the first place. One leads to another. Using a CVS build of a package is far worse in many environments. -- Scott
