jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Cervera (JIRA) <j...@apache.org>
Subject [jira] [Commented] (JCR-2161) Deprecate org.apache.jackrabbit.api.JackrabbitNodeTypeManager in 2.0 and 1.6
Date Fri, 10 Jun 2011 10:08:58 GMT

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

José Cervera commented on JCR-2161:
-----------------------------------

I know this is an old issue, but I don't understand why adding the deprecation in 1.6.X, when
this version is only compatible with JCR-1.0 and the NodeTypeManager interface doesn't offer
any method for registering new nodes.

> Deprecate org.apache.jackrabbit.api.JackrabbitNodeTypeManager in 2.0 and 1.6
> ----------------------------------------------------------------------------
>
>                 Key: JCR-2161
>                 URL: https://issues.apache.org/jira/browse/JCR-2161
>             Project: Jackrabbit Content Repository
>          Issue Type: Wish
>          Components: jackrabbit-api, jackrabbit-core, JCR 2.0
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 2.0.0
>
>
> The JackrabbitNodeTypeManager defines 3 methods that can be removed for version 2.0 since
they are no longer needed:
>     NodeType[] registerNodeTypes(InputSource in)  throws SAXException, RepositoryException;
>     NodeType[] registerNodeTypes(InputStream in, String contentType)  throws IOException,
RepositoryException;
> those deal with directly register nodetypes from a XML or CND source. since we don't
want to support XML serialization any longer, and the CND import can be easily done using
the spi-commons CompactNodeTypeDefReader with the new JCR2.0 node type registration. if the
XML is to be supported, i suggest to detach the reader similar to the CND one.
>     boolean hasNodeType(String name) throws RepositoryException;
> this is now in the JCR2.0 api

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message