You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2010/01/15 14:35:54 UTC

[jira] Commented: (JCR-2161) Remove org.apache.jackrabbit.api.JackrabbitNodeTypeManager in 2.0 and deprecate in 1.6

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

angela commented on JCR-2161:
-----------------------------

this has been requested for 2.0 but was never added to the JCR 2.0 component.
i have the impression that this is half way done (deprecation in 1.x). can we complete that for 2.0 and remove or
at least deprecated the interface in trunk and the 2.0 branch?

> Remove org.apache.jackrabbit.api.JackrabbitNodeTypeManager in 2.0 and deprecate in 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.
-
You can reply to this email to add a comment to the issue online.