Agreed that XML may not be the best language to capture domain
specification expressiveness. But use of XML/XSLT to do
custom code generation has the benifit of rapid application
prototyping and development. The crucial fact is that the
domain specification is captured in XML only relatively few times
and project software developers mainly use the generated code.
The question is how many people in the project is exposed
to 'ugliness' of XML and how many times. The advantages
of 'neat' code generation far outweigh the disadvantages
of 'ugliness' of domain specification in XML.
In a real Network Management Software development I achieved
60% of generated code (EJB, SNMP, Java utilities) by using
custom code generation by XML/XSLT. Only myself dealt with
XML other software developers happily used generated code. You
can imagine the lead the project had and continues to have
because of use of XML/XSLT in project specific custom code
generation. The code generation system is stable now -- any new
addition in EJB, SNMP model results in thousands of lines of
Java/SQL/XML/SVG code without any additional effort.
I would, therefore, continue to recommend the book as worth
exploring. This book really contributed new techniques in
software development. More specically with XML/XSLT you have
freely available tools to implement "model driven programming"
in your software project.