You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/10/19 00:06:44 UTC
[jira] Updated: (JCR-1586) Create org.apache.jackrabbit.api.jsr283
(in jackrabbit-api) and move future jsr283 interfaces and classes there
[ https://issues.apache.org/jira/browse/JCR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1586:
-------------------------------
Issue Type: New Feature (was: Task)
> Create org.apache.jackrabbit.api.jsr283 (in jackrabbit-api) and move future jsr283 interfaces and classes there
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JCR-1586
> URL: https://issues.apache.org/jira/browse/JCR-1586
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-api
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
> Priority: Minor
> Fix For: 1.5.0
>
>
> (as discussed on mailing list)
> as the implementation of the new features for jsr283 have started, i
> suggest to put the new jsr283 interfaces to jackrabbit-api instead to
> core (where possible). this way, we can already figure out
> inter-module dependency issues and people can start using experimental
> features through an API than rather through casting objects to core
> interfaces.
> suggestion: use 'org.apache.jackrabbit.api.jsr283' as base package for
> the new jsr283 interfaces and classes.
> for example, use
> org.apache.jackrabbit.api.jsr283.nodetype.NodeDefinitionTemplate
> for the future javax.jcr.nodetype.NodeDefinitionTemplate
> once jcr2.0 is released, we will drop the interim interfaces.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.