Subjects
Home
Xalan extension functions
Fomatting question serializing DOM with pretty print
xalan with pull parser
Cannot find the declaration
Apache Xalan drop support to run on JRE 1 1 x
Why does Doctype change processing of a document
Node set to XML string via Java extensions in Xalan J: possible?
Templates/Transformers + thread safety???
Problem evaluating xpath with muliple prefix with different namespace
remove an arbitrary attribute from xsl output
Xalan3 XSLT 2 0 XPath 2 0 support?
Problem using compiled translets with Xalan !!
Xalan and jstl 1 1 problem with transform tag
NullPointer in DOM2DTM getLocalName
URIResolvers base parameter with xsltc and cascaded imports
Performance problem for Xalan J on intel dual core
Standard libraries in JAXP?
Serializing a DOM tree to XML file, customize entities replacement
Library Conflict Involving BCEL Library
A question on how users are using <xsl:message >
Kevin Cormier as a new Apache Xalan J committer
Struggling to iterate over tokenized string
Xalan count() trouble
Problem with recursive xpath
Error when switching to java 1 5
document( ' ')
Problem with Xalan2 7 0 transformation
cr/lf options
entity encoded XML
can xalan transform 2 xml using one xslt?
Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
xsl transform with cdata section elements
xslt parameters not expanded
Weird behavior of XPath evaluate()
How to avoid <xsl:message > instruction prints stylesheet file informations ?
Cannot find SimpleTransform subdirectory after installing Xalan J
recover from document not found exceptions
jdk1 5 and Xalan jar differences?
Performance Issue
Error/Bug adding floating point numbers
XPathAPI: eval exp using nodes with default namespace
modifying xalan to output invalid XML
NullPointerException
mege two separate xml nodes into one
Is this a XALAN document identification bug?
is StylesheetRoot really java io Serializable ?
transform() fails for DOMSource but succeeds for StreamSource
Thoughts on Transformer parameter passing
HELP, Xalan and jstl 1 1 problem with transformer
Problem with XPath namespace axis?
string utils:replace deleting search string if replacement string is an HTML
help with enumeration values pls
xalan 2 5 1 vs 2 7 performance question
How to insert/update in XML document
HTML Serialization and Handling of Ampersands in HREF Attributes
XHTML link tag stripping
SystemId Unknown; Line #24; Column #49; java lang NullPointerException
xpath text() help
Apostrophe problem with xalan 2 7 0
How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
java 1.4 endorsed standards

java 1.4 endorsed standards

2003-04-16       - By Alex_Fuller@(protected)
Reply:     1     2     3     4  

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 postmaster@(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.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++