Hello,
So, what has been decided about this matter ?
For what I can see, if the sql2 <-> qom parser is not related to SPI,
it's place in more likely to be in the jcr-commons module. But that's
only what I can see, i'm not part of jackrabbit :) .
Marcel Reutegger (JIRA) a écrit :
[ https://issues.apache.org/jira/browse/JCR-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763931#action_12763931 ]
Marcel Reutegger commented on JCR-2343:
---------------------------------------
AFAICS it does not depend on SPI packages and could be moved to jcr-commons,
but this would also affect public classes that we already released and it would
potentially break existing code when users upgrade to 2.0.
This mainly affects the SQL2 Parser class, other classes were introduced after
the 1.6 release and are not a problem. What do others think? Should we move it
to jcr-commons?
Utility class to tranform JCR-SQL2 to/from JCR-JQOM
---------------------------------------------------
Key: JCR-2343
URL: https://issues.apache.org/jira/browse/JCR-2343
Project: Jackrabbit Content Repository
Issue Type: New Feature
Components: jackrabbit-jcr-commons
Affects Versions: 2.0-alpha12
Reporter: johann sorel
Priority: Minor
The JCR2 doc specify that both contain the same thing and can be translated
from one to another
in a straightforward manner. The jackrabbit-jcr-commons module should offer a
utility class to transform
from one language to another in a generic way,
for exemple :
- String toSQL2(QueryObjectModel qom)
- QueryObjectModel toJQOM(QueryObjectModelFactory factory, String query)
