this is the recommended way... http://xml.apache.org/xalan-j/faq.html#faq-N100CB
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 16, 2003 10:50 AM To: [EMAIL PROTECTED] Subject: java 1.4 endorsed standards According to several of the posts I've seen here, a generally accepted method of overriding the version of xalan/xerces in JDK1.4 is to use the -Xbootclasspath/p: jvm setting. However, http://java.sun.com/j2se/1.4.1/docs/tooldocs/windows/java.html appears to say that doing so may violate the JVM license agreement. An alternative would be to use the endorsed standard override mechanism, -Djava.endorsed.dirs=.... As a side issue, I would have thought that the classes in rt.jar would have still loaded first since they're in the bootclasspath, but they didn't seem to in our testing. Anyway, we found one article that recommended not overriding APIs within Sun's JVM because Sun was far more thorough with testing and would have a very good idea of how the classes interact with the rest of the platform. Does this argument hold water with the xerces/xalan APIs? I guess I'm just curious what other developers are doing. Is it better to be conservative and keep to whatever's been endorsed by Sun, or do the new features/better performance/bug fixes necessitate using newer versions? Thanks, Alex ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This e-mail message and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify LODESTAR Corporation immediately -- by replying to this message or by sending an e-mail to [EMAIL PROTECTED] -- and destroy all copies of this message and any attachments. Thank you. For more information about LODESTAR Corporation, please visit us at http://www.Lodestarcorp.com. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
