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.
jdk1.5 and Xalan.jar differences?

jdk1.5 and Xalan.jar differences?

2007-04-30       - By Erin Harris
Reply:     1     2     3     4  

Hi,

Which JDK are you referring to?

IBM's JDK includes XSLT4J which is based on Xalan.  For JDK 1.5 it is
based on Xalan Java 2.6.0.  So there should be no issue moving from Xalan
to the JDK.

I believe that SUN's JDK 1.5 contains only XSLTC which does not have all
of the features of the Xalan interpretive processor (someone from SUN
please correct this if it is wrong).  The main differences are in
extension support.  XSLTC does not support the following extensions:

dynamic EXSLT extensions
NodeInfo extension functions
SQL library extension
pipeDocument extension
evaluate extension
tokenize extension

If you want to continue to use the Xalan interpreter with SUN's JDK you
can use the endorsed standards override mechanism:
http://java.sun.com/j2se/1.4.2/docs/guide/standards/

Thanks.

Erin Harris





"alapati.sasi" <alapati.sasi@(protected)>
30/04/2007 05:16 AM

To
xalan-j-users@(protected)
cc

Subject
jdk1.5 and Xalan.jar differences?







Hi All,

If i use jdk1.5 instead of xalan.jar what could be the problems i can
expect. i heard that to overcome this we need to put some jar's in
endorsed
directory of jdk . CAN any one tell me the resons why there is a problem
with jdk1.5 builtn xsl transformer.

Thanks & Regard's
Sasi.A
--
View this message in context:
http://www.nabble.com/jdk1.5-and-Xalan.jar-differences--tf3668647.html#a10250510

Sent from the Xalan - J - Users mailing list archive at Nabble.com.




<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">Which JDK are you referring to?</font>
<br>
<br><font size=2 face="sans-serif">IBM's JDK includes XSLT4J which is based
on Xalan. &nbsp;For JDK 1.5 it is based on Xalan Java 2.6.0. &nbsp;So there
should be no issue moving from Xalan to the JDK.</font>
<br>
<br><font size=2 face="sans-serif">I believe that SUN's JDK 1.5 contains
only XSLTC which does not have all of the features of the Xalan interpretive
processor (someone from SUN please correct this if it is wrong). &nbsp;The
main differences are in extension support. &nbsp;XSLTC does not support
the following extensions:</font>
<br>
<ul>
<li><font size=2 face="sans-serif">dynamic EXSLT extensions</font>
<li><font size=2 face="sans-serif">NodeInfo extension functions</font>
<li><font size=2 face="sans-serif">SQL library extension</font>
<li><font size=2 face="sans-serif">pipeDocument extension</font>
<li><font size=2 face="sans-serif">evaluate extension</font>
<li><font size=2 face="sans-serif">tokenize extension</font></ul>
<br><font size=2 face="sans-serif">If you want to continue to use the Xalan
interpreter with SUN's JDK you can use the endorsed standards override
mechanism: </font><a href=http://java.sun.com/j2se/1.4.2/docs/guide/standards/>
<font size=2 color=blue face="sans-serif">http://java.sun.com/j2se/1.4.2/docs
/guide/standards/</font></a><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="sans-serif">Thanks.</font>
<br><font size=2 face="sans-serif"><br>
Erin Harris<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;alapati.sasi&quot;
&lt;alapati.sasi@(protected)&gt;</b> </font>
<p><font size=1 face="sans-serif">30/04/2007 05:16 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">xalan-j-users@(protected)</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">jdk1.5 and Xalan.jar differences?</font><
/table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2><br>
Hi All,<br>
<br>
If i use jdk1.5 instead of xalan.jar what could be the problems i can<br>
expect. i heard that to overcome this we need to put some jar's in endorsed<br>
directory of jdk . CAN any one tell me the resons why there is a problem<br>
with jdk1.5 builtn xsl transformer.<br>
<br>
Thanks &amp; Regard's<br>
Sasi.A<br>
-- <br>
View this message in context: http://www.nabble.com/jdk1.5-and-Xalan.jar
-differences--tf3668647.html#a10250510<br>
Sent from the Xalan - J - Users mailing list archive at Nabble.com.<br>
<br>
</font></tt>
<br>