jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-309) Extract the public API interfaces from o.a.j.core to o.a.j.api
Date Tue, 31 Jan 2006 08:59:36 GMT
     [ http://issues.apache.org/jira/browse/JCR-309?page=all ]

Jukka Zitting updated JCR-309:
------------------------------

    Attachment: jackrabbit-api.patch

Attached a patch for creating public interfaces for RepositoryImpl.shutdown() and WorkspaceImpl.createWorkspace(String).
Does this look OK? If so, I'll go ahead and commit it.

I also investigated the options for doing the same to node type registration. Exposing the
current NodeTypeManagerImpl.getNodeTypeRegistry().registerNodeTypes(Collection) method will
require also the *Def interfaces (optionally also the *DefImpl classes) to be exposed. This
will also bring a dependency to the QName class. Is it OK to expose so much (essentially promising
that they will not change much before Jackrabbit 2.0) or should we create an alternative like
NodeTypeManagerImpl.registerNodeTypes(InputStream)?

> 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


Mime
View raw message