Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] XML Schema: "Best used with the ______ tool"

From: "Michael Kay" <mike@--------.--->
To: "'Dennis Sosnoski'" <dms@--------.--->
Date: 11/28/2008 12:22:00 PM
> Current generation data binding tools unmarshal and marshal 
> as fast or faster than just building or serializing a DOM, 
> and access is much faster and easier than using XSLT or 
> XQuery to access data from said DOM. Have you actually tried 
> any comparisons? Even back six years ago my JiBX data binding 
> was faster than the best of the DOM-type models (dom4j), as 
> discussed in this article: 
> http://www.ibm.com/developerworks/xml/library/x-databdopt2/ 
> Data binding also generally uses much less memory than a DOM 
> model, because only the data values are represented rather 
> than all the details of the XML structure. As for validation, 
> it is rarely used in production systems due to the large 
> performance overhead.

I don't have any performance data, and I would love to see some. But XSLT
and XQuery processors also use tree representations that are much faster and
smaller than a DOM (in one recent Saxon measurement, 40% of the size, 40%
faster to build, and 30 times faster to navigate), and I don't think there's
any intrinsic reason why they should be slower than data binding. I'm not
saying they are faster, just challenging your assertion that they are
impossibly slow - I think the burden of proof is on you.
> 
> XQuery may be usable when you only need a few selected items 
> of data from the documents, but it's not a realistic approach 
> when all the data in the document is actually used by the application.

Why?
> 
> 
> For most web services applications the Java (or other programming
> language) representation is actually primary, and XML is just 
> being used for interchange. 

I don't think it matters which is primary, the complexity comes from having
two representations and keeping them aligned. But I would have thought the
format used for data interchange is primary in the sense that it needs to be
agreed with other parties, whereas the Java representation is under local
control. (Unless of course you're running the same code at both ends, in
which case I'm not sure why you're using XML at all.)

> Do you seriously expect 
> developers to go back to creating DOM representations from 
> their data structures, and vice versa?

Good lord, no! DOM should be allowed to die an undignified, lonely and
miserable death. But I also think that business logic should be written in
4GLs not in 3GLs - 20 years ago we seemed to be more advanced in recognizing
that than we are today.

Michael Kay
http://www.saxonica.com/


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent