27 Aug
2008
27 Aug
'08
5:28 p.m.
Ludovic Dubost wrote:
Does this mean our JCRStore need not support JCR1?
JCRv2 standard final release planed at Sep-2008.
Currently there is some initial (not working) JCRSQL2 parser and
(working) QOM in Jackrabbit trunk.
Jackrabbit will release as RI with JCRv2.
ExoJCRv2 has not JCRSQL2 parser yet, but it planed here:
http://jira.exoplatform.org/browse/JCRS
Actually, only our query system need JCRv2 features. So I'm writing
JCRStore based on JCRv1 standard now.
But all queries will work only on JCRv2. (There is queries in
xwiki-core, platform-web, all products)
Artem Melentyev wrote:
XQL is obsoleted XML Query Language (a parent of XQuery).
http://www.w3.org/TandS/QL/QL98/pp/xql.html
Personally I'm fine with XQL too.
But XWQL seems more concrete and doesn't remind XML,XQuery.
WDOT?
...
I propose:
0) Name: XWiki Query Language, XWQL as a name of the new language.
Why not XQL ? Does it conflict with something ? ...
So the main idea is to use simple JPQL preprocessor to rewrite virtual
data model to real.
This is quite easy for HQL and JCRSQL2. But it is hard(but doable) for
JCRv1 XPath.
I'm not sure we need XPath.. It's deprecated in JCR v2 so we don't
really care. The most important is to have a consitent query api
XWQL or XQL working
the same way for HQL and JCRSQL2.
--
Artem Melentyev