jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2301) CND support in jackrabbit-jcr-commons
Date Wed, 09 Sep 2009 14:02:58 GMT

    [ https://issues.apache.org/jira/browse/JCR-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753096#action_12753096

Alexander Klimetschek commented on JCR-2301:

> 14 commits ... in 2009 only doesn't seem too stable to me

All those commits were related to JCR 2.0 changes or general clean up, not fixing actual parsing
bugs. I think moving all those QNode* classes over to jcr-commons is really a bit of overkill,
if you can get them simply via NodeTypeManager.createNodeTypeTemplate() et al.

Otherwise I think one could share the lexer and an abstract base class for CND reading that
operates on JCR 2.0 NodeTypeTemplate interfaces (and gets them from an abstract method createNodeTypeTemplate(),
same for node defs and property defs). If this will be used by spi-commons as well, it would
be forced to have QNode* to extend from the new JCR 2.0 templates. Or one would provide yet
another wrapper that implements both *Template and QNode* interfaces, internal to the spi
cnd parser.

> CND support in jackrabbit-jcr-commons
> -------------------------------------
>                 Key: JCR-2301
>                 URL: https://issues.apache.org/jira/browse/JCR-2301
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-commons, nodetype
>            Reporter: Jukka Zitting
> It would be nice if the CND parsing functionality in spi-commons could be made available
in jcr-commons for use by JCR clients that shouldn't have to know anything about the SPI.

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

View raw message