XQJ (JSR 225)

[Florent Georges]

Michael Kay wrote:

> The difference between them is that XQPreparedExpression
> contains a compiled expression or query, whereas XQExpression
> merely holds the dynamic context for executing an expression or
> query - despite its name, the expression to be evaluated is not
> held in the XQExpression object, but is always supplied
> dynamically.

  Unfortunately, that's what I thought.

> Whenever I complained about the design (or even the
> nomenclature) I was told it would all seem completely intuitive
> to people who know JDBC.

  That is what I was afraid to hear.  While this is quite true,
it can also be stated as "we kept the same bad design as JDBC, in
that regard."

  I wonder why the design was not based on the JAXP API for XSLT
rather than on JDBC...  There are stuff to be improved over
there, sure, but the concept of compiled object (Templates) and
its representation augmented with dynamic context for evaluation
(Transformer) is very clear.

> Unless you need the portability, I recommend Saxon's s9api
> interface.

  Yep, when I can afford using it, that's what I do usually.  If
well encapsulated, it is not hard to change implementation
anyway.

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/