Order of XML attributes after DOM processing

by

Sorry to say, but the answer is more subtle than “No you can’t” or “Why do you need to do this in the first place ?”.

The short answer is “DOM will not allow you to do that, but SAX will”.

This is because DOM does not care about the attribute order, since it’s meaningless as far as the standard is concerned, and by the time the XSL gets hold of the input stream, the info is already lost.
Most XSL engine will actually gracefully preserve the input stream attribute order (e.g.
Xalan-C (except in one case) or Xalan-J (always)). Especially if you use <xsl:copy*>.

Cases where the attribute order is not kept, best of my knowledge, are.
– If the input stream is a DOM
– Xalan-C: if you insert your result-tree tags literally (e.g. <elem att1={@att1} .../>

Here is one example with SAX, for the record (inhibiting DTD nagging as well).

SAXParserFactory spf = SAXParserFactoryImpl.newInstance();
spf.setNamespaceAware(true);
spf.setValidating(false);
spf.setFeature("http://xml.org/sax/features/validation", false);
spf.setFeature("http://apache.org/xml/features/nonvalidating/load-dtd-grammar", false);
spf.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);
SAXParser sp = spf.newSAXParser() ;
Source src = new SAXSource ( sp.getXMLReader(), new InputSource( input.getAbsolutePath() ) ) ;
String resultFileName = input.getAbsolutePath().replaceAll(".xml$", ".cooked.xml" ) ;
Result result = new StreamResult( new File (resultFileName) ) ;
TransformerFactory tf = TransformerFactory.newInstance();
Source xsltSource = new StreamSource( new File ( COOKER_XSL ) );
xsl = tf.newTransformer( xsltSource ) ;
xsl.setParameter( "srcDocumentName", input.getName() ) ;
xsl.setParameter( "srcDocumentPath", input.getAbsolutePath() ) ;

xsl.transform(src, result );

I’d also like to point out, at the intention of many naysayers that there are cases where attribute order does matter.

Regression testing is an obvious case.
Whoever has been called to optimise not-so-well written XSL knows that you usually want to make sure that “new” result trees are similar or identical to the “old” ones. And when the result tree are around one million lines, XML diff tools prove too unwieldy…
In these cases, preserving attribute order is of great help.

Hope this helps 😉

More Related Contents:

  1. Normalization in DOM parsing with java – how does it work?
  2. Get a node’s inner XML as String in Java DOM
  3. How to save parsed and changed DOM document in xml file?
  4. XML Document to String
  5. What is the shortest way to pretty print a org.w3c.dom.Document to stdout?
  6. HTML/XML Parser for Java [closed]
  7. How to I output org.w3c.dom.Element to string format in java?
  8. Java: Most efficient method to iterate over all elements in a org.w3c.dom.Document?
  9. How to strip whitespace-only text nodes from a DOM before serialization?
  10. Getting XML Node text value with Java DOM
  11. Pretty print XML in java 8
  12. why is sax parsing faster than dom parsing ? and how does stax work?
  13. Unable to read xml with namespace prefix using DOM parser
  14. Create XML document using nodeList
  15. Been staring at my code for an hour and still can't see the issue. Android – Java development [closed]
  16. Generate/get xpath from XML node java
  17. NoClassDefFoundError in Eclipse
  18. JAXB Marshalling Unmarshalling with CDATA
  19. Use custom Manifest file and permission in Unity?
  20. Java implementation of JSON to XML conversion [closed]
  21. How do I append a node to an existing XML file in java
  22. How to fix Invalid byte 1 of 1-byte UTF-8 sequence
  23. Find everything between two XML tags with RegEx
  24. What is XML BOM and how do I detect it?
  25. Generating XML using SAX and Java [closed]
  26. No resource identifier found for attribute ‘layout_behavior’ in package
  27. JAXB inheritance, unmarshal to subclass of marshaled class
  28. Groovy: Create a Map with JAX-B Object’s specific attributes
  29. Is there a SaxParser that reads json and fires events so it looks like xml
  30. White spaces are required between publicId and systemId

Leave a Comment