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.
Standard libraries in JAXP?

Standard libraries in JAXP?

2006-09-05       - By Erin Harris
Reply:     1     2     3     4     5     6  

Hi Siegfried,

The ApplyXPathDOM sample uses the DOM Level 3 XPath API which Sun may not
support (it didn't seem to in the Sun jdk that I have).  The XPathAPI
sample (which does pretty much the same thing) uses JAXP and that seems to
work with Sun's JDK.  See:  
file:///D:/xalan-j_2_7_0/docs/samples.html#applyxpathjaxp

Thanks.

Erin Harris





"siegfried" <siegfried@(protected)>
05/09/2006 01:44 PM

To
<xalan-j-users@(protected)>
cc

Subject
Standard libraries in JAXP?






I can run the ApplyXPathDOM.java sample by making a class path of the jar
files shipped (downloaded) with apache Xalan. Since these are now standard
interfaces (and implementations), why cannot I abandon the jars in Xalan
and just use the implementations in my 1.5 JRE? Can the ApplyXPathDOM.java
run with just the classes in the Sun 1.5 JRE?

Thanks,
Siegfried


<br><font size=2 face="sans-serif">Hi Siegfried,</font>
<br>
<br><font size=2 face="sans-serif">The ApplyXPathDOM sample uses the DOM
Level 3 XPath API which Sun may not support (it didn't seem to in the Sun
jdk that I have). &nbsp;The XPathAPI sample (which does pretty much the
same thing) uses JAXP and that seems to work with Sun's JDK. &nbsp;See:
&nbsp;</font><a href="file:///D:/xalan-j_2_7_0/docs/samples.html#applyxpathjaxp
"><font size=2 color=blue face="sans-serif">file:///D:/xalan-j_2_7_0/docs
/samples.html#applyxpathjaxp</font></a>
<br>
<br><font size=2 face="sans-serif">Thanks.<br>
<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;siegfried&quot; &lt
;siegfried@(protected)&gt;</b>
</font>
<p><font size=1 face="sans-serif">05/09/2006 01:44 PM</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">&lt;xalan-j-users@(protected)&gt;</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">Standard libraries in JAXP?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 face="Arial">I can run the ApplyXPathDOM.java sample by
making a class path of the jar files shipped (downloaded) with apache Xalan.
Since these are now standard interfaces (and implementations), why cannot
I abandon the jars in Xalan and just use the implementations in my 1.5
JRE? Can the ApplyXPathDOM.java run with just the classes in the Sun 1.5
JRE?</font>
<br><font size=2 face="Arial">&nbsp;</font>
<br><font size=2 face="Arial">Thanks,</font>
<br><font size=2 face="Arial">Siegfried</font>
<br>