Re: Early Draft Review: XQuery for Java (JSR 225)
> > There's been discussion here about techniques for passing queries to > > an XQuery processor. There was a suggestion Java programs should > > parse them and pass them as serialized abstract syntax trees (one > > benefit being compile-time type checking). That seems a reasonable > > alternative as an option, but not as a replacement, for sending > > XQuery strings down the wire. > > <sigh/> Miles Sabin wrote: > You should go back and reread Burak Emir's posts a little more carefully: he proposed that the _API_ should have been designed around an abstract model of queries. Okay, Miles, let's break this down. 1. Burak Emir proposed an API re-design to use an abstract representation of queries instead of using XQuery strings. So far we're in agreement. 2. He discussed an approach of parsing queries to produce an abstract syntax tree, serializing that, and passing it to the XQJ driver. (disagree here?) 3. Redesigning the API affects the format of the data stream passed between the XQJ client and the XQuery engine. (disagree here?)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format