• To: xml-dev@l...
• Subject: Re: Early Draft Review: XQuery for Java (JSR 225)
• From: Bill de hÓra <bill.dehora@p...>
• Date: Tue, 22 Jun 2004 23:43:49 +0100
• In-reply-to: <40D8B2F6.3020900@o...>
• References: <20040620080246.RJLE21846.mta08-svc.ntlworld.com@Turtle> <40D6D10F.8010705@e...> <40D720B2.7050004@o...> <40D7FE45.5090808@e...> <40D8B2F6.3020900@o...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a1) Gecko/20040520

[not xposted to jsr-225-comments@j...]


Bob Foster wrote:

> The main advantage of your proposal, OOP orthodoxy aside, seems to be in 
> preventing syntactically incorrect queries. 

No. Syntactic correctness isn't what's valuable, nor is OOP 
conformance. What is valuable is the ability to construct and 
mnaipulate queries dynamically in the target programming language - 
XQuery reflection.


>  On the con side, 
> building up expressions using individual For, Where, etc. classes is 
> certainly going to be clumsier.

Not in my experience. Having access to a syntax tree can be quite 
useful.

cheers
Bill

• Follow-Ups:
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Bob Foster <bob@o...>

• References:
  • RE: Early Draft Review: XQuery for Java (JSR 225)
    • From: "Michael Kay" <michael.h.kay@n...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Burak Emir <Burak.Emir@e...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Bob Foster <bob@o...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Burak Emir <Burak.Emir@e...>
  • Re: Early Draft Review: XQuery for Java (JSR 225)
    • From: Bob Foster <bob@o...>

• Prev by Date: Re: Early Draft Review: XQuery for Java (JSR 225)
• Next by Date: Re: Early Draft Review: XQuery for Java (JSR 225)
• Previous by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Next by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Index(es):
  • Date
  • Thread