You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2009/09/09 14:27:57 UTC

[jira] Commented: (JCR-2301) CND support in jackrabbit-jcr-commons

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

Michael Dürig commented on JCR-2301:
------------------------------------

Initially the CND parser moved from core to spi-commons. See JCR-1516. 

The parser is useful for both JCR and SPI. So there will always be an additional dependency. Since SPI implementations almost always depend on jcr-commons anyway, moving the parser might be a good idea. 

However, the different representations of Names, Types etc would have to be factored out. Currently the parser uses builders for constructing the types (QNodeDefinitionBuilder, QNodeTypeDefinitionBuilder, QPropertyDefinitionBuilder). These would need to be generalized. Both jcr-commons and spi-commons need to provide their specific versions for these builders. 

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