jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "johann sorel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2343) Utility class to tranform JCR-SQL2 to/from JCR-JQOM
Date Fri, 09 Oct 2009 08:16:31 GMT

    [ https://issues.apache.org/jira/browse/JCR-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763905#action_12763905
] 

johann sorel commented on JCR-2343:
-----------------------------------

That's a solution, I agree, but not an available one for us.

I guess this case is special for our applications. 
Our analyze of jackrabbit has show us the fact that jackrabbit-SPI is to far from JCR.
Since we are making a JCR implementation for our data model (Geographic Information Systems)
we choose to limit our use of jackrabbit to the JCR-commun module.
There are four main reasons why we don't wont to depend on jackrabbit spi.
- First it's to far from the JCR specification, it's like a second jcr definition.
- We have to learn jackrabbit spi, which is a useless extra step because we want jcr, not
spi.
- We lose the control over the code, we have no control over cache, real JCR object, nodes,
node types and so on. Spi makes an automatic mapping to jcr interfaces that we don't control.
- And it adds more dependency where we already have more than 40Mb of jars

My question now : 
Is the code handling JQOM/SQL2 really binded to SPI or is it generic/abstract enough to be
moved in jackrabbit-jcr-common ?

> 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)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message