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

RE: Article on JAXP 1.3 "Fast and Easy XML Processing"

• To: "'Chris Burdess'" <dog@b...>,<Neeraj.Bajaj@S...>
• Subject: RE: Article on JAXP 1.3 "Fast and Easy XML Processing"
• From: "Michael Kay" <mike@s...>
• Date: Tue, 15 Feb 2005 14:16:42 -0000
• Cc: <xml-dev@l...>
• In-reply-to: <fc8c236db086182efac90c1331b25854@b...>
• Thread-index: AcUTW76QGT9wYU9+SB+EpKcnSopyiwADHt7A

> You talk about the benefits of an "object model neutral" 
> XPath API, yet 
> provide no examples of how any object model other than W3C DOM might 
> work. DOM already provides its own XPath API, and I'm 
> guessing that by 
> promoting the JAXP version you believe it's a better solution. Could 
> you provide any reasons for us to use and/or implement both 
> APIs? What 
> other object models might be supported, and if they're so important, 
> why does JAXP not have core support for them?

JAXP is an interface, not an implementation (something that the Sun people
who packaged it for release sadly forgot.)

Saxon includes an implementation of the JAXP 1.3 XPath and validation APIs,
supporting four different object models: DOM, JDOM, XOM, and Saxon's
NodeInfo model. The benefit is that it enables you to write an application
that can access any of these models.

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

• References:
  • Re: Article on JAXP 1.3 "Fast and Easy XML Processing"
    • From: Chris Burdess <dog@b...>

• Prev by Date: Re: Master Foo explains XML to aliens
• Next by Date: Re: Master Foo explains XML to aliens
• Previous by thread: Re: Article on JAXP 1.3 "Fast and Easy XML Processing"
• Next by thread: Re: Article on JAXP 1.3 "Fast and Easy XML Processing"
• Index(es):
  • Date
  • Thread