jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2161) Remove org.apache.jackrabbit.api.JackrabbitNodeTypeManager in 2.0 and deprecate in 1.6
Date Fri, 19 Jun 2009 14:30:07 GMT

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

Marcel Reutegger commented on JCR-2161:
---------------------------------------

+1

> 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
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 1.6.0, 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.


Mime
View raw message