XML parsers with JDK1.5

Does anyone know if the xml parsers that are shipped with JDK1.5 conform to DOM level2 or DOM level3 specification? I am not sure how to locate the parser that is shipped with the JDK either!

Thanks ! It says the parser is xerces, but does not tell which version of xerces!

Similar Messages

Xml Exception with JDK1.5

I wrote some code using java 1.4.2 on a linux machine and it works fine .
Now I am using the same code using JDK 1.5 on a slorais machine.And it is raising following exception
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
Does any one have any idea?

Hi
I've got the same problem with jdk 1.5 and tomcat 5.0 and I've found the problem
in tomcat java is called with the following argument:
-Djava.endorsed.dirs="X:\my_app\Portal\tomcat\common\endorsed"
In this directory you find two jar files: xercesImpl.jar and xml-apis.jar needed by tomcat and that must be loaded before all xmsl stuff present in the jdk (1.4 naming problem). And in the file xml-apis.jar the TransformerFactoryImpl is set to "org.apache.xalan.processor.TransformerFactoryImpl".
The solution: remove the file xml-apis.jar from the directory.
For other application, just check this file or dom3-xml-apis.jar in your class path

Experiences with Adobe XPAAJ, XML Parsers, OC4J /AS 10.1.2,10.1.3 and DB10g

Over the past couple of weeks we have been working on a solution which uses the newly available adobe XPAAJ api's (XML/PDF Access API for Java) for Java.
The client has a legacy requirement to where users are issued with a pdf form which they complete, save and upload to the server via a JSP. A neat bit of Java code utilizing the XPAAJ API's then strips out the form entered data and spits out XML. This is then parsed and inserted into relational tables within the schema.
Our solution needs to be deployed to an Oracle stack. However we ran into a number of problems when deploying the solution to AS 10.1.2. The adobe API's are not compatible with the Oracle XML Parsers. When extracting the form data, no error is reported and the code which performs the xml parsing just fails. Very nasty.
The main problem has been that Oracle XDK libraries have been hard-coded into the classpath of the container using the referential JAR file Class-Path mechanism. Altering this has required the use of the JRE extension library mechanism, or altering the boot classpath of the JVM when it is launched to load the alternative XML parser implementation instead. While this works, it has been an unsupported operation since the effect of this change is not limited to a specific application – it’s effect are felt across the entire container and this may lead to unpredictable results at runtime.
~http://www.oracle.com/technology/tech/java/oc4j/10131/how_to/how-to-swapxmlparser/doc/readme.html
We did look at a number of other solutions including embedding the java classes I'd written into the database. After loading the apache Xerces api's into our schema we hit upon the same problem. It seems that the same thing happens in the database and the Oracle XML parser is used by default.. Please see SR Number : 6153038.994 on Metalink.
If you can upgrade to AS 10.1.3 then you can follow the excellent how to at:http://www.oracle.com/technology/tech/java/oc4j/10131/how_to/how-to-swapxmlparser/doc/readme.html . Demo code can be found at: http://www.oracle.com/technology/tech/java/oc4j/10131/how_to/how-to-swapxmlparser/how-to-swapxmlparser.zip
The how-to details how to swap xml parsers within the application server.
Other possible solutions that are also available include:
- Shelling out to the OS from the DB or Apps Server, You can then execute the app as a command line app with a custom classpath. Very bad architecture design.
- Setting up an RMI client / server application where client is the db or apps server. You can find examples of this on the web. google 'Simple RMI example'.
- Bootstrapping the XML parser in AS 10.1.2 (unsupported).
I hope people have found this informative. It might save someone a lot of time.
Message was edited by:
Kris Jones

"When I was installing SOA 10.1.3.1.0 on oracle 10.2.0.1 and it was giving error that it needs minimum 10.2.0.3, just wondering 10.1.2.0.2 + SOA =will this work?"
so you talk about the db version. SOA 10.1.3.x runs on 10.2.0.1 and above (I ran for the longest time on XE) and if I remember correctly that's a warning, and not a hard prereq.
Regarding Appserver versions - soa 10.1.3 runs on AS 10.1.3 only

Exception with javax.xml.parsers.FactoryConfigurationError

I have a code segment that is working in a Java standalone application environment. I've taken the same segment and ran it in Lotus Domino's environment, with the following error,
javax.xml.parsers.FactoryConfigurationError: java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader)
Can anyone help?

I changed a switch within the Lotus Domino environment to allow class loader, but now I'm getting a different error,
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found
Any idea?

How to validate xml file with XSD schema ?? in JDK1.4.2

How to validate xml file with XSD schema ?? in JDK1.4.2
i dont want to use new Xerec Jar ...
Suggest option ...

Please do not double-post. http://forum.java.sun.com/thread.jspa?threadID=5134447&tstart=0
Then use Stax (Woodstock) or Saxon.
- Saish

Weblogic 12g Server - EAR with WAR - how can I have different XML parsers

Hi All,
I have a requirement where I need to have two different XML parsers in the same enterprise application.
By backend Spring container require a XML parser and my JSP code which has XSLT logic require another XML parser.
If I specify -D System property then it is applied to the whole Enterprise application. Instead I want a way to specify different XML parsers one for Spring backend container and the other for JSP pages.
I am deploying my application in Weblogic and it is an EAR file.
Thanks in Advance,
Kishore Veleti A.V.K.

check this one.
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl

ParserConfigurationException with javax.xml.parsers.DocumentBuilderFactory

Like many people, I am trying to just read in the contents of a XML file. My code compiles in WS studio and I publish it to the server. However, I keep getting a ParserConfigurationException when I try to get a DocumentBuilder from the factory. Below is my code:
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
try {
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse( new File(XMLFILE) );
Any idea why?

The xmlfile is valid and here is the partial stacktrace
Root Error-1: javax/xml/parsers/ParserConfigurationException
java.lang.Exception: javax/xml/parsers/ParserConfigurationException
at Search5F_Results_jsp_5._jspService(_Search_5F_Results_jsp_5.java:206)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:390)
at org.apache.jasper.runtime.JspServlet.serviceJspFile
Do I need to set some system property?

XML validation with DTD in java 1.5 not supporting

Hi,
I am facing a problem regarding validation of xml file with DTD tag in it.
I have disabled the parser through setValidating(false) method.
xml file is not parsed in JRE 1.5.but it is parsed in JRE 1.6.
Why this is showing such a behavior?
I have used xerces 2.9.0,xml-api.jar and other jar regarding XML api but still it is giving error.
please help me.
please provide a jar file name or its issue resolution in jre 1.5 or 1.4.

thanks for your prompt reply.
I required that it should be completely disabled in jre 1.5(jdk1.5 or 1.4).
I am using DOM Parsing.I have currently disabled with follwowing method,
builderFactory.setValidating(false);
builderFactory.setFeature("http://xml.org/sax/features/validation",
     false);
     builderFactory.setFeature("http://apache.org/xml/features/nonvalidating/load-dtd-grammar", false);
     builderFactory.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd",false);
     builderFactory.setFeature("http://xml.org/sax/features/external-general-entities", false);
     builderFactory.setFeature("http://xml.org/sax/features/external-parameter-entities", false);
     factory.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);
in 1.6 it is working fine but I required that i have to disabled it.but it is giving a error in jre1.5.
Exception in thread "main" java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
I just want to disable the parsing in jdk version 1.5 or 1.4
thanks in advance
anand

Java.lang.NullPointerException javax.xml.parsers.DocumentBuilder.parse

Hi all,
i have a problem by solving an error in my code. The Code is mainly from Ian Darwin.
The code i am running works with j2sdk1.4.2_04. But now i have to bring it to work with jdk1.6.0_13.
The code parses xml documents. With small xml documents the code works. With large xml documents i get the following error while running the produced class file.
Exception in thread "main" java.lang.NullPointerException
at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.setChunkIndex(DeferredDocumentImpl.java:1944)
at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.appendChild(DeferredDocumentImpl.java:644)
at com.sun.org.apache.xerces.internal.parsers.AbstractDOMParser.characters(AbstractDOMParser.java:1191)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.characters(XMLDTDValidator.java:862)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:463)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:208)
at XParse.parse(XParse.java:38)
at XParse$JFileChooserrv.<init>(XParse.java:119)
at XParse.main(XParse.java:213)
I know what a java.lang.NullPointerException mens. But i don't know where i have to look for. Specially i don't know what or where "com.sun.org.apache...." is.
Is there a package that a have to add to the environment? Can some one tell my where i can find this package?
I wrote the code for some years ago, 2006 or so. With the knew jdk1.6.0_13 some thinks chance in the environment. Couldn't find what exactly.
The code has only 215 lines, but some how i can't add it to this Message, because Maximum allowed is only 7500.
Is there an other Forum, which may is better for my question?

Here is the code:
import java.io.*;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.xml.sax.*;
import javax.swing.*;
import java.awt.event.*;
import java.io.*;
import java.util.*;
import javax.swing.*;
import java.awt.Container;
import javax.swing.JTextArea;
* This code is mainly from @author Ian Darwin, [email protected]
public class XParse {
     /** Convert the file */
     public static void parse(File file, boolean validate) {
          try {
               System.err.println("");
               String fileName = file.getAbsolutePath();
               System.err.println("Parsing " + fileName + "...");
               // Make the document a URL so relative DTD works.
               //String uri = new File(fileName).getAbsolutePath();
               //System.err.println(uri);
               DocumentBuilderFactory f = DocumentBuilderFactory.newInstance();
               if (validate)
               f.setValidating(true);
               DocumentBuilder p = f.newDocumentBuilder();
               p.setErrorHandler(new MyErrorHandler(System.err));
               //XmlDocument doc = XmlDocument.createXMLDocument(file);
               boolean vaild = p.isValidating();
               if (vaild) {
                    System.out.println("yes parsing");
                    Document doc = p.parse(file); // <<<< ERROR
               System.out.println("Parsed OK");
          } catch (SAXParseException ex) {
               System.err.println("+================================+");
               System.err.println("|       *SAX Parse Error*        |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
               System.err.println("At line " + ex.getLineNumber());
               System.err.println("+================================+");
          } /**catch (RuntimeException ex) {
               System.err.println("+================================+");
               System.err.println("|       *SAX Parse Error*        |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
               //System.err.println("At line " + ex.getLineNumber());
               //System.err.println("At line " + ex.getMessage());
               System.err.println("+================================+");
          }**/ catch (SAXException ex) {
               System.err.println("+================================+");
               System.err.println("|          *SAX Error*           |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
               System.err.println("+================================+");
          /*}} catch (SAXNotRecognizedException ex) {
               System.err.println(" no SAX");*/
          } catch (ParserConfigurationException ex) {
               System.err.println(" ???");
           } catch (IOException ex) {
               System.err.println("+================================+");
               System.err.println("|           *XML Error*          |");
               System.err.println("+================================+");
               System.err.println(ex.toString());
private static class JFileChooserrv {
     JFileChooserrv(JFrame f, boolean vverabreiten) {
          String openfile;
          String verror;
          boolean validate = true;
          final JFrame frame = f;
          String vFilename = "Z:\\Boorberg\\parsen_vista\\daten";
          //String vFilename = "C:\\";
          File vFile = new File(vFilename);
          final JFileChooser chooser = new JFileChooser(vFile);
          JFileFilter filter = new JFileFilter();
          filter.addType("xml");
          filter.addType("sgml");
          filter.addType("html");
          filter.addType("java");
          filter.setDescription("strukturfiles");
          chooser.addChoosableFileFilter(filter);
          boolean vjeas = true;
          chooser.setMultiSelectionEnabled(vjeas);
          int returnVal = chooser.showOpenDialog(frame);
          if (returnVal == JFileChooser.APPROVE_OPTION) {
               //Array filearry[] = chooser.getSelectedFiles();
               //if (vFile = chooser.getSelectedFiles()) {
               //File file[] = chooser.getSelectedFiles();
               File vfile[] = chooser.getSelectedFiles();
               //String openfile = new String();
               int vlenght = vfile.length;
               if (vlenght>1) {
                    int x=0;
                    while (x< vlenght) {
                              parse(vfile[x], validate);
                              x = x +1;
               if (vlenght<=1) {
                    File v2file = chooser.getSelectedFile();
                         parse(v2file, validate);
          } else {
               System.out.println("You did not choose a filesystem           object.");
     System.exit(0);
private static class JFileFilter extends javax.swing.filechooser.FileFilter {
     protected String description, vnew;
     protected ArrayList<String> exts = new ArrayList<String>();
     protected boolean vtrue;
     public void addType(String s) {
          exts.add(s);
     /** Return true if the given file is accepted by this filter. */
     public boolean accept(File f) {
          // Little trick: if you don't do this, only directory names
          // ending in one of the extentions appear in the window.
          if (f.isDirectory()) {
               return true;
          } else if (f.isFile()) {
               Iterator it = exts.iterator();
               while (it.hasNext()) {
                    if (f.getName().endsWith((String)it.next()))
                         return true;
          // A file that didn't match, or a weirdo (e.g. UNIX device file?).
          return false;
     /** Set the printable description of this filter. */
     public void setDescription(String s) {
          description = s;
     /** Return the printable description of this filter. */
     public String getDescription() {
          return description;
private static class MyErrorHandler implements ErrorHandler {
        // Error handler output goes here
        private PrintStream out;
        MyErrorHandler(PrintStream out) {
            this.out = out;
         * Returns a string describing parse exception details
        private String getParseExceptionInfo(SAXParseException spe) {
            String systemId = spe.getSystemId();
            if (systemId == null) {
                systemId = "null";
            String info = "URI=" + systemId +
                " Line=" + spe.getLineNumber() +
                ": " + spe.getMessage();
            return info;
        // The following methods are standard SAX ErrorHandler methods.
        // See SAX documentation for more info.
        public void warning(SAXParseException spe) throws SAXException {
               //System.exit(0);
            //out.println("Warning: " + getParseExceptionInfo(spe));
        public void error(SAXParseException spe) throws SAXException {
               //System.exit(0);
            String message = "Error: " + getParseExceptionInfo(spe);
            throw new SAXException(message);
        public void fatalError(SAXParseException spe) throws SAXException {
               //System.exit(0);
            String message = "Fatal Error: " + getParseExceptionInfo(spe);
            throw new SAXException(message);
     public static void main(String[] av) {
          JFrame vframe = new JFrame("chose files to pars");
          boolean vverabreiten = true;
          boolean validate = true;
          JFileChooserrv vdateienwaehlen = new JFileChooserrv(vframe, vverabreiten);
}The Stack Trace i posted in the last Message. But i couldn't read it, i am not a programmer.

Package javax.xml.parsers does not exist

When I compile the sample program for xml, DOMEcho.java, or any other xml java program, I get errors on the import statements.
For all the import statements within java.xml.* I get an error message such as: package javax.xml.parsers does not exist.
I have my path and classpath variables set as follows.
REM Java initialization
SET PATH=c:\Documents and settings\User\jwsdp-1_0_01\bin;c:\j2sdkee1.3.1\bin;c:\jdk1.3.1_01\bin;%PATH%
SET JAVA_HOME=c:\j2sdkee1.3.1_01
SET JAVA_XML_PACK_HOME=c:\java_xml
SET JAXM_HOME=c:\java_xml\java_xml_pack-summer-02_01\jaxm-1.1_01
SET JAXP_HOME=c:\java_xml\java_xml_pack-summer-02_01\jaxp-1.2_01
SET JAXR_HOME=c:\java_xml\java_xml_pack-summer-02_01\jaxr-1.0_02
SET JAXRPC_HOME=c:\java_xml\java_xml_pack-summer-02_01\jaxrpc-1.0_01
SET CLASSPATH=c:\Documents and settings\User\jwsdp-1_0_01\bin;c:\Documents and settings\User\jwsdp-1_0_01
SET CLASSPATH=%CLASSPATH%;c:\jdk1.3.1_01\bin;c:\jdk1.3.1;
SET CLASSPATH=%CLASSPATH%;c:\java_xml\java_xml_pack-summer-02_01\jaxm-1.1_01;
SET CLASSPATH=%CLASSPATH%;c:\java_xml\java_xml_pack-summer-02_01\jaxp-1.2_01;
SET CLASSPATH=%CLASSPATH%;c:\java_xml\java_xml_pack-summer-02_01\jaxr-1.0_02;
SET CLASSPATH=%CLASSPATH%;c:\java_xml\java_xml_pack-summer-02_01\jaxrpc-1.0_01
Any ideas?

Now that the first program compiled I tried another sample program:
StandAlone.java and
got the same errors.
* $Id: StandAlone.java,v 1.10 2002/04/06 00:47:31 mode Exp $
* $Revision: 1.10 $
* $Date: 2002/04/06 00:47:31 $
* Copyright 2002 Sun Microsystems, Inc. All rights reserved.
* SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This program starts with...
import java.io.*;
import javax.xml.soap.*;
import java.net.URL;
import javax.mail.internet.*;
import javax.xml.transform.*;
import javax.xml.transform.stream.*;
import org.dom4j.*;
* A StandAlone JAXM Client.
public class StandAlone {

Javax.xml.parsers not found in import

I have downloaded JAXP from java.sun.com. I put the jar files in ../jdk/jre/lib/ext/.
Im getting "javax.xml.parsers not found in import" when I try to compile a program with an import statement like this:
import javax.xml.parsers.*;
What am i missing? My classpath has ../jdk/jre/lib/ext/ in it..

I have downloaded JAXP from java.sun.com. I put the
jar files in ../jdk/jre/lib/ext/.
Im getting "javax.xml.parsers not found in import"
when I try to compile a program with an import
statement like this:
import javax.xml.parsers.*;
What am i missing? My classpath has
../jdk/jre/lib/ext/ in it..Hi,
This seems to be a classpath problem. You can also use JDK1.4.1
which has crimson bundled with it. So you do not need to do any explicit settings for classpath.
Pls let me know if you still have problems
Thanks,
Bhakti

NoSuchMethod: javax.xml.parsers.SAXParserFactory.getSchema()

Hi All,
In a servlet I have created a SOAPMessage object based on the request received, and when I execute
message.getSOAPBody I get the message:
java.lang.NoSuchMethodError: javax.xml.parsers.SAXParserFactory.getSchema()
I am running tomcat with jdk 1.5 and I am using saaj-api.jar, saaj_imp.jar and Fastinfoset.jar from jwsdp 1.6
Anyone got any ideas what to do ?
Kind regards,
Marco Laponder

Along with jdk1.4.2, Sun has bundled a currently ancient version of JAXP.
So, get a recent version of a JAXP implementation (e.g. with JWSDP1.6), probably contained in jar-files called jaxp-api.jar, dom.jar, sax.jar, xalan.jar and xercesImpl.jar, and add these to your classpath when you're compiling/running.
You're not done yet! Because the old jaxp libraries are bundled with your JVM, the classloader will find them through your bootclasspath, and they will be prefered above the new implementation you just added to the classpath. To resolve this, the JVM creators came up with the endorsed mechanism. This allows you to provide new classes for a list of predefined packages. These classes are already included in the jvm distribution, but are foreseen to be updated. See for more information about the endorsed mechanism: http://java.sun.com/j2se/1.4.2/docs/guide/standards/ .
So to be short, you also have to make the jvm recognise them as endorsed libraries. E.g. by adding them to the <java-home>/lib/endorsed directory or by setting the java.endorsed.dirs property to the directories which include the new jar files.
Your commandline to run app.class would become: java -Djava.endorsed.dirs=/home/endorsedDir;/anotherDir app

Javax.xml.parsers package

I am not able to find the javax.xml.parsers package even after installing J2EESDK on top of Jdk1.3 . Can any one point me to the right place to download this package?
Thanks

The said package is part of Java API for XML Processing. i.e. JAXP
If you use J2EE SDK 1.3, the said package comes with the SDK. So you should find it in j2ee.jar
Maybe its just that you do not have j2ee.jar in your classpath.
If you are using J2EE SDK 1.2.1, you will have to downaload and install JAXP http://java.sun.com/xml/download.html

What is the SAX2 Driver that comes with JDK1.4?

What is the SAX2 Driver that comes with JDK1.4?
Thanks,
Aaron

The following are SAX2 System Property values for org.xml.sax.driver (used when implementing XMLReaderFactory):
Xerces2 - org.apache.xerces.parsers.SAXParser
Crimson - org.apache.crimson.parser.XMLReaderImpl
Per the Xerces2 documentation the SAX2 Parser in Xerces2 will implement the same package name as Xerces to maintain backward compatibility. Will applications that implement the Crimson SAX2 driver in the JDK 1.4 be hosed once Xerces2 is implemented in the JDK?
The SAX2 driver provided with the JDK will change from org.apache.crimson.parser.XMLReaderImpl to org.apache.xerces.parsers.SAXParser. That will put many SAX2 applications at risk if the programmer is relying on a SAX2 driver provided with the JDK.
Is a solution to this issue being worked on?
Thanks,
Aaron

How can I save a XML file with JAXP1.1?

Dear All.
I write a program to create XML file with DOM model, but I can't know how to save it? My environment is JAXP1.1 and JDK1.3.1,I has been required not use other XML parser toolkits,only JAXP1.1.
How can I do? thank you.
Many person give me a idea the com.sun.xml.tree.XmlDocument, but I can't find the class in API document or JAXP1.1's packages. why?
what is it? How can i use it?
thank you very much.

The way to save an XML Document is using a Transformer.
To have access to a transformer use the packages :
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
Then for saving your Document Object (named dXml) get a Transformer Object with the TransformerFactory Object :
TransformerFactory tf = TransformerFactory.newInstance();
Transformer t = tf.newTransformer();
Now you have got your Transformer Object, to save your Document Object use the method :
Document dXml = getMyDocument(); // this is your Document Object.
OutputStream osSave = getMySaveStream(); // this the OutputStream you need to save your Document.
try
t.transform(new DomSource(dXml), new StreamResult(new OutputStreamWriter(osSave)));
finally
osSave.close();
And your Document was now saved.

XML parsers with JDK1.5

Similar Messages

Maybe you are looking for