jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-190) Use JCR API defined by JSR-333
Date Fri, 08 Nov 2013 11:12:24 GMT

     [ https://issues.apache.org/jira/browse/OAK-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela updated OAK-190:
-----------------------

    Attachment: OAK-190.patch

patch changing the jcr dependency from 2.0 to the latest version of jsr 333 as available from
the corresponding svn repository.

apart from 2 trivial methods in the NamespaceRegistry and NodeType i didn't implement any
of the new methods defined by JSR-333 (-> throw UnsupportedOperationException). The aim
of the patch is to give us a better idea what kind of features have been added by JSR 333
and such allowing us to evaluate if it would be beneficial to implement some of them (apart
from the changes to ac mgt which have been implemented already).
it might also give us an idea if we would run into troubles if we have to support JSR 333
later on.

Note, that the patch does not add dummy implementations for the following new interfaces present
with JSR-333:

- RepositoryManager (see Workspace#getRepositoryManager)
- EventFilter
- EventJournal
- LockInfo

while i have some questions security wise e.g. wrt to Workspace#getRepositoryManager and VersionManager#removeVersionHistory
i still think it's worth the effort to quickly evaluate the impact JSR 333 has on the OAK
repository even if then decide not to support most of the functionality in a first release.

> Use JCR API defined by JSR-333
> ------------------------------
>
>                 Key: OAK-190
>                 URL: https://issues.apache.org/jira/browse/OAK-190
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, jcr
>            Reporter: angela
>         Attachments: OAK-190.patch
>
>
> there are quite some improvements in JSR-333 (both spec and api wise) and
> i think it would make sense to develop jackrabbit3 on the latest version
> of the specification.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message