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.

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-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.

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.

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.

Using the EnvironmentCheck utility: To help diagnose classpath problems and also determine which version of Xalan-Java is being used, try running Xalan-Java's environment checking utility, checked in at xml-xalan/java/src/org/apache/xalan/xslt/EnvironmentCheck. Be sure to run EnvironmentCheck in the environment where you are experiencing the problem.

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.

Xalan is an XSLT stylesheet processor for transforming XML documents into HTML, text, or other XML document types.

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

It is not that straight forward by using JAXP DOM api. Here is a minimal XML, but element, text, attribute are included. The code is compilable, runnable, and produce the desired result except the indentation. If you want it indented nicely, you need to use a modified identity template to do the transformation. Output to String method is also provided.

present the Mozilla control implements IHTMLDocument, IHTMLElement & IHTMLElementCollection. It should be possible to walk the DOM quite satisfactorily, as well as call get_all and other methods that return a collection. You may also write to a document with calls to open, write, writeln, & close on IHTMLDocument. You may also call setAttribute, getAttribute & removeAttribute on elements asl well as get the className & id but not set them.

The Document Object Model is a platform and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure, and style of documents. The DOM for SVG allows for straightforward and efficient vector graphics animation via scripting. A rich set of event handlers such as onmouseover and onclick can be assigned to any SVG graphical object.

Yes, though the hierarchy of objects will follow the Mozilla model (i.e. DOM 1) and not Internet Explorer. The differences may require changes to applications hardcoded to expect the IE model. Other methods may be implemented but many return E_NOTIMPL. I would welcome patches to improve this support.

TODO - there should be a table listing what interfaces the control supports & major methods but at the moment there is no such thing. The best that can be done for now, is to look at the actual implementation of the DOM objects in mozilla/embedding/browser/activex/src/common on lxr.mozilla.org and check if interface or method X is actually supported.