Xerces provides XML parsing and generation. Fully validating parsers are available for both Java and C++, implementing the W3C XML and DOM (Level 1 and 2) standards, as well as the de facto SAX (version 2) standard

The Xalan-Java 1 compatibility API has been deprecated and now purged, so you must use the Xalan-Java 2 API. We strongly encourage you to use the JAVAX 1.1/TrAX API. For more information ,see the next FAQ. The JDK 1.3 automatically places everything in the lib/ext directory in front of everything you place on the classpath. If this directory contains a version of DOM, JAXP, or Xerces that predates the Xalan-Java distribution you are using, you may have problems! The IBM JDK 1.

The Xalan-Java version 1 compatibility API has been deprecated and removed, so you must use the Xalan-Java version 2 API. We strongly encourage you to use the Java API for XML Processing (JAXP) 1.3. For more information, see the FAQ on TrAX and JAXP. The JDK 1.3 automatically places everything in the lib/ext directory in front of everything you place on the classpath.

Xerces-C++ is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability to read and write XML data. Like Xalan-C++, Xerces-C++ is available from the Apache XML site: http://xml.apache.org/xerces-c/index.html

JBindery, part of MRJ SDK 2.1, is used to create a double-clickable Java application with the necessary configuration information built in. It is analogous to writing a .bat or .sh script. Click on the "Add .zip File" button and add both the "Xerces-J.jar" and "Xerces-JSamples.jar" files. Enter "dom.DOMWriter" as the Class name. Enter "data/personal.xml" in the Optional parameters box.

will do the trick, provided you set your CLASSPATH correctly. If you are using j2sdk1.4.1_01, it will be always right as long as you can use java. In j2sdk1.4.1_01, xml stuff is bundled inside rt.jar already. My xerces/crimson parser does not validate for me? The following code does not work, why? org.apache.xerces.parsers.SAXParser parser = new org.apache.xerces.parsers.SAXParser(); // MyDefaultHandler extends DefaultHandler parser.setContentHandleler(new MyDefaultHandler()); parser.

While this question is not exactly about XSD or the C++/Tree mapping and it is covered in the Xerces-C++ Programming Guide, this step is a prerequisite to some more advanced techniques covered in this FAQ. Furthermore, the XSD runtime provides some untilities that make the code a little bit more palatable. #include <xercesc/dom/DOM.hpp> #include <xsd/cxx/xml/string.hxx> #include <xsd/cxx/xml/dom/elements.

The Xalan DOM implementation is highly optimised for transformations. However, whilst you can build documents in the Xalan DOM, subsequent modification will not work. The Xalan DOM is designed to be either an input or an output from a transformation, not as a general DOM implementation. So in cases where you want to simply transform documents using Xalan, using the internal DOM implementation is the best approach.

The most useful tip applies to any updated code that you import into the VisualAge for Java 2.0 product. Before updating code, do the following: Deleting code from your workspace does not actually delete the code permanently -- the versioned code is moved to the repository where it can be retrieved later. Be aware, though, that removing code from your workspace will cause problems with all of the other classes that use that code. VisualAge for Java 2.

Running JavaPureCheck on the Xerces-J parser code indicated 339 pure Java classes, 9 warnings, and 0 errors. The nine warnings are enumerated below with explanations. To see the entire report, click here. There are many common cases where JavaPureCheck issues warnings even though the code is pure Java. These are the most common reasons: Program code calls the Class.forName(String) method to dynamically load a class file. In this situation, the specified class may contain impure Java code.

Yes and no. It actually depends. When requiring pretty printing during marshalling, Castor will internally use Apache's Xerces to implement this feature. As such, when not using this feature, Xerces is not a requirement, and any JAXP-compliant XML parser can be used (for unmarshalling).

No. Starting with release 1.1, we have added support for using the Xerces instance as shipped with the JRE/JDK for serialization. As such, for Java 5.0 users, this removes the requirement to download Xerces separately when wanting to use 'pretty printing' with Castor XML during marshalling. To enable this feature, please change the following property in your local castor.

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.

You have concepts problems. JAXP is just standard interfaces for you to use any JAXP compliant Java parser. And xerces is just one of them What you need to do? Move your code to most recent stable build xerces first. Make as less changes as possible. Test your application during the move, don't break your application. If something does not work, fix it. Move to JAXP after that, actually not much left. Search the files for xerces. Change them to its parent interfaces or superclass in JAXP.

Very strange. For example, when I run "SAX2Print" (one of the example programs for using the SAX2 parser provided by Xerces), I get the following output: The first "visibleTo" attribute is the one I actually put on the <handler> element inside my .XML file. The second one is the default value specified for the <handler> element in the .XSD (W3C schema defition) file. far as I can tell, these duplicate attributes happen in the following situation: 1. Using the Xerces SAX2 parser 2.

While this question is not exactly about XSD or the C++/Tree mapping and it is covered in the Xerces-C++ Programming Guide, this step is a prerequisite to some more advanced techniques covered in this FAQ. Furthermore, the XSD runtime provides some untilities that make the code a little bit more palatable. The code presented in this entry can also be found in the multiroot example in the examples/cxx/tree/ directory of XSD distribution. #include <istream> #include <xercesc/dom/DOM.