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

Re: [proposal] XPath API for Java

• To: xml-dev@l...
• Subject: Re: [proposal] XPath API for Java
• From: ari@c... (K. Ari Krupnikov)
• Date: 20 Sep 2003 12:45:37 -0700
• In-reply-to: <3F6C9777.6000300@d...>
• References: <3F6C9777.6000300@d...>
• Sender: ari@l...
• User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Bill de hÓra <bill@d...> writes:

> Hi,
> 
> I've been through a ton of DOM-in-Java programming in the last 12
> months. You learn early on to use XPaths where possible to keep the
> code flexible and clean. But one of the annoying about using XPath in
> Java is that it's all library specific.

> So here's a proposed api:
> 

>    public interface XPath

>      List match( Node target, String xpath, Map namespaces );

I think an interface with only a single method is of limited value,
given the range of XPath uses.

One thing I'd consider is a convenience method getSingleNode with the
same arguments - to eliminate the unnecessary cast (I realize things
will change in 2.0, but I hear some folks are sticking with 1.0). I
wasn't sure which List you refer to from the import statements; I
wouldn't use java.util.List because of the casting - consider the
better-typed NodeList.

I would also consider getBooleanValue() and getStringValue(). Also to
consider - what kind of exception will this class throw, for malformed
XPath strings, for instance. Will it be a subclass of DOMException?
Use a non-standard error code? many DOM application only declare
DOMException in their methods.

Ari.

• Follow-Ups:
  • Re: [proposal] XPath API for Java
    • From: Bill de hÓra <bill.dehora@p...>

• References:
  • [proposal] XPath API for Java
    • From: Bill de hÓra <bill@d...>

• Prev by Date: Re: Pushing all the buttons
• Next by Date: Re: some days I'm wrong
• Previous by thread: [proposal] XPath API for Java
• Next by thread: Re: [proposal] XPath API for Java
• Index(es):
  • Date
  • Thread