[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Re: Native XML Interfaces

• From: Andrew Welch <andrew.j.welch@gmail.com>
• To: "Timothy W. Cook" <timothywayne.cook@gmail.com>
• Date: Mon, 3 Jun 2013 12:12:46 +0100

On 3 June 2013 12:02, Timothy W. Cook <timothywayne.cook@gmail.com> wrote:
> On Mon, Jun 3, 2013 at 5:34 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote:
>>
>> +1  Pretty much exactly my experience too.  They reach for binding
>> first, then bemoan xml in general after they hit all the usual
>> problems with the binding approach.
>>
>> And the only reason they reach for binding, is because of a lack of
>> knowledge of the apis out there, or the lack of a familiar api to use.
>
> My experience with binding tools (JAXB, PyXB, generateDS) has been
> less than useful.
> The code they create is almost impossible to trouble shoot and they do
> not support advanced XML Schema concepts.
>
> But Andrew, maybe I include myself in that category of not being aware
> of the APIs that are available. Could you exand on that with a couple
> of examples?

For example the dev is faced with the challenge of extracting the
<title> and product/@id values from some xml.

They could:

- use xquery/xpath
- use xom/jdom
- use sax/stax

instead they use a tool to generate an xsd from the xml, then use a
binding tool to generate some classes, then use those generated
classes.


-- 
Andrew Welch
http://andrewjwelch.com

• Follow-Ups:
  • Re: Re: Native XML Interfaces
    • From: "Pete Cordell" <petexmldev@codalogic.com>
  • Re: Native XML Interfaces
    • From: Norman Gray <norman@astro.gla.ac.uk>
  • Re: Re: Native XML Interfaces
    • From: "Timothy W. Cook" <timothywayne.cook@gmail.com>

• References:
  • Re: Re: Native XML Interfaces
    • From: Andrew Welch <andrew.j.welch@gmail.com>
  • Re: Re: Native XML Interfaces
    • From: "Timothy W. Cook" <timothywayne.cook@gmail.com>