[ http://issues.apache.org/jira/browse/JCR-309?page=comments#action_12364607 ]
Tobias Bocanegra commented on JCR-309: -------------------------------------- ok. lets add the register nodetype. but i would prefer an 'org.xml.sax.InputSource' instead of the input stream. and maybe an additional content type: public NodeType[] NodeTypeManagerImpl.registerNodeTypes(InputSource in, String contentType); contentType is either: text/xml or text/cnd the advantage of the inputsource is: it has a systemId that can be used to resolve entities (eg: relatvie DVDs), and also for better error reporting. > Extract the public API interfaces from o.a.j.core to o.a.j.api > -------------------------------------------------------------- > > Key: JCR-309 > URL: http://issues.apache.org/jira/browse/JCR-309 > Project: Jackrabbit > Type: Task > Components: API > Reporter: Jukka Zitting > Fix For: 1.0 > Attachments: jackrabbit-api.patch > > To better document and track the public JCR extensions and component API > provided by Jackrabbit and to allow more room for refactoring within the > Jackrabbit core, we shoud move (or create) the supported API interfaces to a > new org.apache.jackrabbit.api package. > At least the following interfaces should be moved along with any supporting > implementation-independent classes: > * PersistenceManager > * FileSystem > * AccessManager > * QueryHandler > * TextFilter > Possible dependencies to implementation-specific classes should preferably be > abstracted using extra interfaces. > Also the workspace and node type administration methods should be published > as Jackrabbit-specific extensions to the JCR API interfaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
