Hi Jeff Friesen,
More questions, but now about XML.
How has XML processing changed since the first version of the book? It's there new additions/improvements with the new versions of Java?
How XML is being used in the industry in the modern software development?
Is there any advice of When to favor XML over YAML, or other modern alternatives when writing tools or software intended to consume structured data representations?
I don't think that XML processing has changed much since the first edition. If anything, I'd say that JSON is doing better than XML, and YAML is doing better than JSON. I say this based on the trend information for XML, JSON, and YAML at Google Trends (trends.google.com).
I haven't discovered anything new regarding XML in the Java SDK. Regarding XPath and XSLT, Java still supports only version 1.0 even though XPath and XSLT have evolved through subsequent versions. I've updated Chapter 6 to discuss installing SAXON in order to access post XSLT/XPath 1.0 features.
I think it is good to know XML for those times when you need to work with legacy software that includes XML. Otherwise, you might be better off focusing on JSON. I cannot speak for YAML because I haven't worked with it, and it's outside the scope of the book. Perhaps a third edition might be titled "Java XML and JSON and YAML et al." ;-).
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database