[jira] Commented: (JCR-1697) Simple Google style query
[ https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840119#action_12840119 ] johann sorel commented on JCR-1697: --- "GQL is already in jcr-commons, so the purity is broken. " So there is an issue here. is it too late to move it out ? "Anyway, my principal problem is that I can ..." It looks like it's no big deal for you, it's a matter of modularity. what's the purpose of making maven module if you don't split things properly ? > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1697) Simple Google style query
[ https://issues.apache.org/jira/browse/JCR-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839877#action_12839877 ] johann sorel commented on JCR-1697: --- "GQL" has no relation with JCR. it is just a candidate amoung several others (like Common Query Language or Contextual Query Language) to write a query. See : http://www.loc.gov/standards/sru/specs/cql.html CQL and GQL are not part of the JCR, and having the "Google" name in it does give it any rights to live in the JCR common module. If you need another query language I suggest you add it in a different module, this way you won't force everyone to have it if they don't want it. Some of my projects rely on the jcr-commun module and I hope it will remain dedicated to "pure" JCR. > Simple Google style query > - > > Key: JCR-1697 > URL: https://issues.apache.org/jira/browse/JCR-1697 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-jcr-commons >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 1.5.0 > > > In the Sling project there's a need for a simple query language. See > SLING-573. > I've created a parser that translates the simple query into an XPath query > statement and executes it on a JCR workspace. > I'll commit it to the jackrabbit-jcr-commons module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2343) Utility class to tranform JCR-SQL2 to/from JCR-JQOM
[ 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.
[jira] Commented: (JCR-2343) Utility class to tranform JCR-SQL2 to/from JCR-JQOM
[ https://issues.apache.org/jira/browse/JCR-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763885#action_12763885 ] johann sorel commented on JCR-2343: --- the two methods : qom.getStatement(); qm.createQuery(sql2, Query.JCR_SQL2); Are part of JCR interfaces, They don't do any work unless you implement them. What I was trying to say is that a basic implementation should be provided in the jackrabbit-jcr-commons module. That's why I suggest a QueryUtilities class could be made for this purpose since it's straightforward code. > 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.
[jira] Created: (JCR-2343) Utility class to tranform JCR-SQL2 to/from JCR-JQOM
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.
[jira] Created: (JCR-2342) Missing constants in JCRConstants
Missing constants in JCRConstants - Key: JCR-2342 URL: https://issues.apache.org/jira/browse/JCR-2342 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-jcr-commons Affects Versions: 2.0-alpha12 Reporter: johann sorel Priority: Trivial there are also several missing constants in class JCRConstants in jackrabbit 2.0-alpha12. (All constants coming from the new types of JCR2) here is a small list (It's not a complete list) : public static final String NT_ADDRESS = "nt:address"; public static final String MIX_CREATED = "mix:created"; public static final String MIX_LANGUAGE = "mix:language"; public static final String MIX_LASTMODIFIED = "mix:lastModified"; public static final String MIX_MIMETYPE = "mix:mimeType"; public static final String MIX_TITLE = "mix:title"; public static final String JCR_HOST = "jcr:host"; public static final String JCR_PROTOCOL = "jcr:protocol"; public static final String JCR_PORT = "jcr:port"; public static final String JCR_REPOSITORY = "jcr:repository"; public static final String JCR_WORKSPACE = "jcr:workspace"; public static final String JCR_ID = "jcr:id"; public static final String JCR_CREATEDBY = "jcr:createdBy"; public static final String JCR_LASTMODIFIEDBY = "jcr:lastModifiedBy"; public static final String JCR_TITLE = "jcr:title"; public static final String JCR_DESCRIPTION = "jcr:description"; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
