Apache Xerces2 XML parser download?

Hello all,
where can i find Apache Xerces2 XML parser download?
Seems not working http://xerces.apache.org/xerces2-j/download.cgi
http://xerces.apache.org/xerces2-j/
thank you.
I really need it.
I am stuck with that bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6551600
Edited by: 811911 on 14 févr. 2011 05:41
Edited by: 811911 on 14 févr. 2011 05:52

http://xerces.apache.org/mirrors.cgi#binary
Also needs to be under Java 1.6

Similar Messages

Xml Parser download

Hi all,
Anybody Please tell me where can I download XML parser ?
I have to download and install an XML parser that is compatible with the Java API for XML Parsing (JAXP) 1.1 specification to run struts Program.
Please give the absulute url......
Thanks in advance.
Please rePly soon
Amitindia

there is one built into the jdk. 1.4/1.5 at least.
If you want a separate jar for some reason, or more doc help, try
http://xerces.apache.org/xerces2-j/

Since I updated Firefox 4, I cannot open any attachments in my Gmail, whether Word or PDF files, I can only view them. When trying to download attachments I get an error message: "XML Parsing Error:undefined entity. Help!

The full error message is the following:
XML Parsing Error: Undefined entity
Location chrome://mozapps/content/downloads/unknown content type.xul
Line Number 30, Column 18

In order to use ''nxm://'' links, Nexus Mod Manager must be installed and associated with the ''nxm'' protocol.
* http://www.nexusmods.com/skyrim/mods/modmanager/
In case of problems with this third-party program, please refer to its support forum:
* http://forums.nexusmods.com/index.php?/forum/1413-nmm-code-development-chat

I used to use SpeedBit Video Downloader with Mozilla Firefox, but suddenly a problem happened, I can not download with it now at all as there is an code error appears in the bar of SpeedBit like "XML Parsing Error: unclosed token Location: chrome://browse

I used to use SpeedBit Video Downloader with Mozilla Firefox, but suddenly a problem happened, I can not download with it now at all as there is an code error appears in the bar of SpeedBit like "XML Parsing Error: unclosed token Location: chrome://browser/content/browser.xul Line Number 1, column 8702:....................."
I did evrey thing, but the same problem
reinstall SpeedBit, reinstall Mozilla Firefox.
So what can I do!
== This happened ==
Every time Firefox opened
== 4 days ago

look people, i may have a solution for this. This happened to me a few times before and resolved alone, but last time it happened was when i turned off my router and back on while my comp was running and appeared when i tried opening firefox after that. so wat i did was i shutdown the computer and the router and tried turning both on again, and it resolved.
Therefore, Summary: Shutdown computer then turnoff router then turn both back on
Hope this helps anyone.

How to download sun XML parser/Where to find the parser itself to downloa?.

I saw the website below. But I do not have a clue of what to download and where to store any files in my directories and how to set the classpaths to run the file below.
http://java.sun.com/developer/earlyAccess/xml/index.html
to run this program
import java.io.File;
import com.sun.xml.parser.Resolver;
import com.sun.xml.tree.XmlDocument;
import org.xml.sax.InputSource;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
public class Simpleparser
public static void main (String argv [])
InputSource input;
XmlDocument doc;
}

The date on that page is 2002-10-14. It is totally obsolete. If you saw examples using a parser whose name starts with "com.sun" then those examples are totally obsolete as well.
If you're using Java 1.4 then it already includes an XML parser. Just look for Java XML tutorials that are more recent and read them. You don't need to download anything.

Apache XML Parser

In WebLogic 6.0, the Apache XML Parser (Xerces) and XSLT engine (Xalan) were contained
in the xmlx.jar file. They are not in this JAR file in the WLS 6.1 beta. Are
these classes no longer shipped with WebLogic Server?

Hi Shannon,
Yes, we include a built-in XML parser closely based on Apache 1.3.1 in WLS.
If you use JAXP without any specific configurations, you will be using this
parser. We also include a Xalan-2.0.1-based XSLT engine which is also
accessed via JAXP.
-Todd
Shannon Schupbach <[email protected]> wrote in message
news:3b1f94dc$[email protected]..
>
In WebLogic 6.0, the Apache XML Parser (Xerces) and XSLT engine (Xalan)were contained
in the xmlx.jar file. They are not in this JAR file in the WLS 6.1 beta.Are
these classes no longer shipped with WebLogic Server?

XML Parsing Error when diplaying the downloads window

After upgrading to the 3.6.15 version everytime I open the downloads window the following text is displayed:
XML Parsing Error: unclosed token
Location: chrome://mozapps/content/downloads/downloads.xul
Line Number 83, Column 5: <menuitem id="menuitem_show"
----^

After upgrading to the 3.6.15 version everytime I open the downloads window the following text is displayed:
XML Parsing Error: unclosed token
Location: chrome://mozapps/content/downloads/downloads.xul
Line Number 83, Column 5: <menuitem id="menuitem_show"
----^

How can I use a 3rd party XML parser such as xerces with OC4J ?

Hi all tech experts,
I am using Oracle Application Server 10g Release 2 (10.1.2) and i have
installed Portal and Wireless and OracleAS Infrastructure on the same
computer.
i tried all the solutions on this thread
Use of Xerces Parser in out application with Oracle App Server 9.0.4
but still fighting.
I have also posted this query on OTN on following thread
How can I use a 3rd party XML parser such as xerces with OC4J?
but no reply....
Please help me on this issue.
Since OC4J is preconfigured to use the Oracle XML parser which is xmlparserv2.jar.
i have read the following article which states that
OC4J is preconfigured to use the Oracle XML parser. The Oracle XML parser is fully JAXP 1.1 compatible and will serve the needs of applications which require JAXP functionality. This approach does not require the download, installation, and configuration of additional XML parsers.
The Oracle XML parser (xmlparserv2.jar) is configured to load as a system level library of OC4J through it's inclusion as an entry in the Class-Path entry of the oc4j.jar Manifest.mf file. This results in the Oracle XML parser being used for all common deployment and packaging situations. You are not permitted to modify the Manifest.mf file of oc4j.jar.
It must be noted that configuring OC4J to run with any additional XML parser or JDBC library is not a supported configuration. We do know customers who have managed to successfully replace the system level XML parser and the Oracle JDBC drivers that ship with the product, but we do not support this type of configuration due to the possibility of unexpected system behavior and system errors that might occur from replacing the tested and certified libraries.
If you absolutely must use an additional XML parser such as xerces, then you have to start OC4J such that the xerces.jar file is loaded at a level above the OC4J system classpath. This can be accomplished using the -Xbootclasspath flag of the JRE.
i have also run the following command
java -Xbootclasspath/a:d:\xerces\xerces.jar -jar oc4j.jar
but no success.
How could i utilize my jar's like xerces.jar and xalan.jar for parsing instead of OC4J in-built parser ?
All reply will be highly appreciated.
Thnx in advance to all.
Neeraj Sidhaye
try_catch_finally @ Y !

Hi Neeraj Sidhaye,
I am trying to deploy a sample xform application to the Oracle Application Server (10.1.3). However, I encountered the class loader issue that is similar to your stuation. I tried all the three solutions but the application is still use the Oracle xml paser class. I am wondering if you have any insight about this?
Thanks for your help.
Xingsheng Qian
iPass Inc.
Here is the error message I got.
Message:
java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
Stack Trace:
org.chiba.xml.xforms.exception.XFormsException: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
     at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
     at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
     at org.chiba.xml.xforms.Container.initModels(Unknown Source)
     at org.chiba.xml.xforms.Container.init(Unknown Source)
     at org.chiba.xml.xforms.ChibaBean.init(Unknown Source)
     at org.chiba.adapter.servlet.ServletAdapter.init(ServletAdapter.java:153)
     at org.chiba.adapter.servlet.ChibaServlet.doGet(ChibaServlet.java:303)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:719)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
     at org.chiba.xml.xforms.Instance.iterateModelItems(Unknown Source)
     at org.chiba.xml.xforms.Bind.initializeModelItems(Unknown Source)
     at org.chiba.xml.xforms.Bind.init(Unknown Source)
     at org.chiba.xml.xforms.Initializer.initializeBindElements(Unknown Source)
     at org.chiba.xml.xforms.Model.modelConstruct(Unknown Source)
     at org.chiba.xml.xforms.Model.performDefault(Unknown Source)
     at org.chiba.xml.xforms.XFormsDocument.performDefault(Unknown Source)
     at org.chiba.xml.xforms.XFormsDocument.dispatchEvent(Unknown Source)
     at org.apache.xerces.dom.NodeImpl.dispatchEvent(Unknown Source)
     ... 18 more

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

Nls support with oracle xml parser in java

I'm using The JAXP interface to manipulate xml with xsl. the implementation that I use is Oracle xml parser.
My xml contains a lot of hebrew chars, and in the result stream each char translated into 5-6 chars, which makes the result to be 5-6 times bigger than it suppose to be, and harder for me to debug my application.
The client's browser shows the results well.
How can I make the transformator to transform the hebrew chars to hebrew char istead of longer and not readable string ?

Oracle XML Team wrote:
: Stephen Flinter (guest) wrote:
: : Environment: WinNT 4.0/SP4, Apache 1.3.6, JServ 1.0, Oracle
: 8.1.5
: : I have downloaded the new Java v2 XML Parser (2.0.2), and
have
: : replaced the wrapper.classpath entry in my jserv.properties
: file
: : with the path to the new parser.
: : When I rerun the "Employee Page" demo, I get the following
: : exception message:
: : [15/09/1999 11:02:22:974 GMT] java.lang.NoSuchMethodError:
: : oracle.xml.parser.v2.XSLProcessor: method
: : processXSL
: (Loracle/xml/parser/v2/XSLStylesheet;Loracle/xml/parser
: : /v2/XMLDocument;)Lorg/w3c/dom/DocumentFragment; not found
: : at oracle.xml.xsql.XSLHelper.process(XSLHelper.java:34)
: : at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java,
: : Compiled Code)
: : at
: : javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
: : at
: : javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
: : at
: : org.apache.jserv.JServConnection.processRequest
: (JServConnection.j
: : ava)
: : at
: : org.apache.jserv.JServConnection.run(JServConnection.java)
: : at java.lang.Thread.run(Thread.java:479)
: : This demo was works fine with the parser shipped with the
: : xsql_servlet download.
: : Regards,
: : Steve
: Version 2.0.2 uses the August XSLT WD which is incompatible
with
: the April WD on which our previous releases including the demos
: were based.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
Hi,
Can someone from the Oracle XML Team point us to a fix so we can
continue our testing???
Steve...
null

XML Parsing in Java Stored Proc--Oracle XML Support Installation?

I am working with a third party product that is having difficulty running a java stored proc that is parsing a supplied XML file. The proc basically looks like:
import java.io.IOException;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import org.w3c.dom.Document;
import org.xml.sax.SAXException;
InputStream is = getXMLAsInputStream(xml);
try {
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse( is );
... parse the document ....
catch (FactoryConfigurationError e) {
// unable to get a document builder factory
We are running on 9.2.0.6, HP-UX 64-bit. At first, when we would attempt to run the proc, a database hang would occur; now after attempting to install using loadjava jars for xerces2.6: ORA-29532: Java call terminated by uncaught Java exception:
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found)
The vendor says that the errors we are getting when running are not due to any dependency on xerces or jre1.4, and that we need to "install Oracle XML support", but I'm not certain what this means (I cannot find any documentation on what to install). I believe that there are jars that need to be loaded into the database to support the XML parsing, as jre1.3 does not include built-in XML support, and Oracle 9.2.0.6 uses jre1.3.
So...does anyone have any thoughts as to how to resolve the missing references? Is there a way to "install Oracle XML support", or is it to install the necessary jars?
Thanks,
Candi

Candi,
The following resources should be of help:
Oracle9i Database Release 2 (9.2) Documentation Library
In particular, check out the following:
Java Developer's Guide
Java Stored Procedures Developer's Guide
XML API Reference - XDK and Oracle XML DB
XML Database Developer's Guide - Oracle XML DB
XML Developer's Kits Guide - XDK
If that doesn't help, then try the following:
OracleJVM and Java Stored Procedures
XML Technology Center
Good Luck,
Avi.

Jstl xml parser not working

i cant seem to be able to select the values from the imported xml file and i dont understand why?
my jsp page:
<%@ page import="java.util.*;" %>
<%@ page contentType="text/html; charset=ISO-8859-5" %>
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<html>
<head>
 <title>Interactive Experience Database - Template 1</title>
 <LINK REL="STYLESHEET" TYPE="text/css" HREF="style.css">
</head>
<body>
<FORM>
<c:import var="xmlfile" url="/cv.xml"/>
<x:parse var="doc" xml="${xmlfile}"/>
<x:out select="$doc/cv/ContactInfo/PersonName"/>
</form>
</body>
</html>the xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cv>
<cv>
<ContactInfo>
 <PersonName>Donald Smith</PersonName>
</ContactInfo>
</cv>

thanks, one thing that annoys me is that that apache
make it so hard to download anything, finding the
binary is so time consuming, ive been looking for the
last half hour. its a jokeI kind of agree with you that for certain projects it is a little difficult to find the stable release of the binaries. I personally find it very time consuming to locate the binary for JSTL 1.1 , and finding the binary for Xalan seems a little more easier than finding the one for JSTL 1.1
For Xalan I was quickly able to locate it through google:
Searched for "download apache xalan" , then Google showed me
http://xml.apache.org/xalan-j/downloads.html then I clicked on :
http://www.apache.org/dyn/closer.cgi/xml/xalan-j
~~~~~~~~~~~~~~~~~~~~~~
But for JSTL 1.1 it took quite a number of steps :
Searched on Google for : "download JSTL 1.1"
First link showed:
http://java.sun.com/products/jsp/jstl/downloads/index.html
Shows the link for Standard 1.0 instead of Standard 1.1
(A newbie to JSTL wouldn't know that there's a 1.1 final release download available)
another link for the same keywords takes me to:
http://jakarta.apache.org/taglibs/
Then I click on downloads: http://jakarta.apache.org/taglibs/#Downloads
but it only shows Nightly Builds downloads not the stable release ones.
Then I click on JSTL1.1 on the left nav takes me to
http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html
The download link finally takes me to:
http://people.apache.org/builds/jakarta-taglibs/nightly/
which is again nightly
Then I carefully read and finally see:
Download the Binary Distribution of the Final Release:
http://jakarta.apache.org/site/downloads/index.html
Then I click on TagLibs
http://jakarta.apache.org/site/downloads/downloads_taglibs.html
and pick Standard 1.1 Tag lib (assuming that is JSTL 1.1)
http://jakarta.apache.org/site/downloads/downloads_taglibs-standard.cgi
I guess I could report this issue to Apache Taglibs and have them make it more efficient to locate the download for the Taglibs.

XML parser for Java setup

I download the XML Parser for Java 3.2.1 Release from the IBM site and I have JDK1.3 installed on my Windows 2000 PC. I've placed the files "xerces.jar" and "xalan.jar" in the location specified by the extensions mechanism (i.e "C:\JDK1.3\jre\lib\ext\").
I downloaded an example where java uses XML but I get an error because it fails to import the following class:
import com.ibm.xml.parser.Parser;
Also in another application the same thing happens with this class:
import com.ibm.xml.parser.TXDocument;
If I remove the xerces and xalan JAR files from the directory mentioned above I get move errors so I presume I have the files in the right location. Do I need to place any other files in that DIR other than the xerces and xalan JAR files?
Any help greatly appreciated!

Not sure if you solved your problem.
I think Xerces was handed over to the Apache organisation by IBM and the package names were then changed so that com.ibm would have become org.apache or whatever. At a guess nobody got round to changing the examples.

JRE 1.4.2: how to override the default xml parser?

Hi all,
I have JRE 1.4.2_03 and I need to replace the default xml "crimson" parser with xerces because the former one doesn't properly handle utf-8 BOM.
Does anyone have an idea where I should look at for this kind of configuration?
I skimmed thorugh the oracle docs but couldn't find anything.
I found a link describing how to change the xml parser in OC4J, but my understanding is that this has little to do with what I am looking for.
I need to force Saxon 8.6.1, that is invoked by means of java.exe from the command line, to pick up the right xml parser.
Has anyone else tried this out already?
Alternatively, is it safe to install JRE 1.5 in place of JRE 1.4.2 on a Oracle 10.1.0.4 database?
I am told that JRE 1.5 uses a different xml parser that should fix my problem.
Bye,
Flavio

I sorted this out myself.
Downloaded the latest stable xerces binary (2.5.0) from http://xml.apache.org/dist/xerces-j/
Then I extracted xercesImpl.jar and put it under:
%ORACLE_HOME%\LIB\endorsed
I had to create the endorsed folder as it didn't exist.
Then, when invoking Saxon using java.exe, I added the following switch:
-Djava.endorsed.dirs=%ORACLE_HOME%\LIB\endorsed
That's it.
You can find some background info on:
https://jaxp.dev.java.net/Updating.html
Bye,
Flavio

DOM XML parser program

Hi,
I am trying to write a sample program using DOM xml parser in java to read the values in a XML file.
please suggest me what are all the things I have to do for that.
I know Java and XML. I want to know how to access values from XML file in java.
Thanks
Selvakumar

Study up on the javax.xml.parsers API here at Sun. Next, download Xerces from Apache (xml.apache.org). Finally, take a tutorial.
- Saish

Apache Xerces2 XML parser download?

Similar Messages

Maybe you are looking for