Hi,
+1 for new packages in jackrabbit-api, with a clear warning that the interfaces
will be removed again as soon as JSR 283 is final. We might want to write that
those are only used for development and testing and must not be used by client code.
regards
marcel
Tobias Bocanegra wrote:
hi,
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 can either extend them from the 'real'
interfaces or just drop them. in any case it might make sense to mark
them as deprecated from start.
WDYT?
--
regards, toby
