Announcement Announcement Module
Collapse
No announcement yet.
Comparison of Java/XML Binding Mechanisms Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Comparison of Java/XML Binding Mechanisms

    Hi,

    I am evaluating Spring WS for an upcoming project and I find myself unsure of which of the available Java/XML Binding mechanisms I should use. In the ideal world I would dig deeply into each one and perform my own comparison, but alas, time may not permit that luxury. So ... I'm wondering if anyone has input they would like to share regarding their experiences with the binding mechanisms supported by Spring WS ... pros/cons, strengths/weaknesses, etc. Or if someone knows of a reasonably recent, reasonably comprehensive white paper or the like comparing available binding mechanisms, I would be interested in that as well. I found one or two on the web, but most of them were from several years ago and the landscape has changed significantly since that time. Thanks in advance.

    Bill Bailey
    Senior Developer / DBA
    Northland, A Church Distributed

  • #2
    Well, there are some hints in the reference docuentation, and there is this page: https://bindmark.dev.java.net/old-index.html

    But it's quite old, i.e. the page hasn't been updated since December 2005.

    Comment


    • #3
      There is a performance comparison slide in these presentation notes.

      http://www.sosnoski.com/presents/cle...clean-soap.pdf

      May be a little biased as the author is a JiBX contributor.

      It is a good read regardless.

      [Edit]

      May also be a little out of date- just noticed the copyright is 2002-2004. Not sure when the presentation was.

      I find jaxb xjc to be fine for my uses.

      Comment


      • #4
        Thought I'd share the following URL's which I found in my web search for information on data binding frameworks and related topics. They are from a series of articles by Dennis Sosnoski, creator of the JiBX framework and although they go back a ways, they seem (so far) to provide a pretty good overview of the topic and some pretty solid comparisons of advantages and disadvantages of different approaches and performance (although things may have changed in that regard in recent months or years).

        The first two are actually comparing different document models for working with the XML 'in the raw', but serve as a good starting point for gaining an understanding of some of the issues involved and why data binding might be a good idea.

        http://www-128.ibm.com/developerwork...ava/index.html
        http://www-128.ibm.com/developerwork...ary/x-injava2/

        The next one is an overview of Castor as an example of the binding mapping approach to data binding.

        http://www-128.ibm.com/developerwork...tor/index.html

        The next two compare a variety of databinding frameworks based on their respective approaches, ease of use, performance, etc.

        http://www-128.ibm.com/developerwork...opt/index.html
        http://www-128.ibm.com/developerwork...pt2/index.html

        The last two are on JiBX architecture and usage, respectively.

        http://www-128.ibm.com/developerwork...bd3/index.html
        http://www-128.ibm.com/developerwork...bd4/index.html

        Obviously, one should consider the possibility of bias on the part of the author since he has a vested interest in promoting one of the analyzed frameworks (JiBX), but so far I haven't seen anything to suggest blatant biases on his part and the articles are full of good information even though they are also 3-5 years old. Hope they are useful to someone else but me.

        Comment


        • #5
          Java XML binding

          Basically there are two approaches:

          1) Schema based
          2) 'Bean' or 'OO' based

          1 - The first I think has as killer application xml payloads that are interchanged by two or more entities as 'contracts' and practically never changes.

          2- The second it's useful when you want to 'serialize' your beans properties for example before enqueing a message in a JMS topic.

          But as it happens frequently all depends by the requirements of your application.

          However I'm using JAXB happily.

          Comment

          Working...
          X