atom feed26 messages in org.apache.jackrabbit.dev[jr3 optional features]
FromSent OnAttachments
Michael DürigFeb 22, 2012 10:31 am 
Julian ReschkeFeb 22, 2012 11:23 am 
Christian StockerFeb 22, 2012 10:47 pm 
Angela SchreiberFeb 23, 2012 12:17 am 
Felix MeschbergerFeb 23, 2012 1:24 am 
Thomas MuellerFeb 23, 2012 1:49 am 
Felix MeschbergerFeb 23, 2012 1:55 am 
Thomas MuellerFeb 23, 2012 2:03 am 
Felix MeschbergerFeb 23, 2012 2:08 am 
Ard SchrijversFeb 23, 2012 2:46 am 
Thomas MuellerFeb 23, 2012 2:59 am 
Ard SchrijversFeb 23, 2012 3:26 am 
Michael DürigFeb 23, 2012 3:33 am 
Julian ReschkeFeb 23, 2012 4:14 am 
Thomas MuellerFeb 23, 2012 4:43 am 
Ard SchrijversFeb 24, 2012 1:36 am 
Thomas MuellerFeb 24, 2012 2:23 am 
Ard SchrijversFeb 24, 2012 2:58 am 
Thomas MuellerFeb 24, 2012 3:19 am 
Ard SchrijversFeb 27, 2012 1:42 am 
Alexander KlimetschekFeb 28, 2012 5:17 am 
Michael DürigFeb 28, 2012 6:18 am 
Stefan GuggisbergFeb 28, 2012 8:58 am 
Michael DürigFeb 28, 2012 10:41 am 
Alexander KlimetschekFeb 28, 2012 2:51 pm 
Michael DürigFeb 28, 2012 5:08 pm 
Subject:[jr3 optional features]
From:Michael Dürig (mdue@apache.org)
Date:Feb 22, 2012 10:31:09 am
List:org.apache.jackrabbit.dev

Hi,

Another point that came up at last week's F2F was that jr3 should - in contrast to jr2 - not implement all optional features of the JCR specification. Rather should we concentrate on the "core" features and improve them wrt. jr2.

With core features I refer to the features which have proven vital in applications using Jackrabbit. With improvements I mean issues we identified with core features (e.g. the notable performance degradation with big list of direct child nodes).

Looking at the list of repository descriptors [1] we could decide for either of them what we want to support. Here is my take:

write.supported = true

identifier.stability = identifier.stability.session.duration

option.xml.export.supported = true option.xml.import.supported = true

option.unfiled.content.supported = false

option.versioning.supported = true option.simple.versioning.supported = true

option.activities.supported = false option.baselines.supported = false option.access.control.supported = true option.locking.supported = true (but we might want make exceptions in a clusterd environment) option.observation.supported = true option.journaled.observation.supported = true option.retention.supported = false option.lifecycle.supported = false option.transactions.supported = true option.workspace.management.supported = true option.update.primary.node.type.supported = true option.update.mixin.node.types.supported = true option.shareable.nodes.supported = false option.node.type.management.supported = true (but with restriction wrt. nodes type in use) option.node.and.property.with.same.name.supported = true node.type.management.inheritance = true node.type.management.inheritance.minimal = ? node.type.management.inheritance.single = true node.type.management.inheritance.multiple = ? node.type.management.overrides.supported = ? node.type.management.primary.item.name.supported = true node.type.management.orderable.child.nodes.supported = false node.type.management.residual.definitions.supported = true node.type.management.autocreated.definitions.supported = true node.type.management.same.name.siblings.supported = false node.type.management.property.types = ? node.type.management.multivalued.properties.supported = true node.type.management.multiple.binary.properties.supported = true node.type.management.value.constraints.supported = false node.type.management.update.in.use.suported = false query.languages = ? query.stored.queries.supported = ? query.full.text.search.supported = true query.joins = ? level.1.supported = true level.2.supported = true option.query.sql.supported = ? query.xpath.pos.index = ? query.xpath.doc.orderable = ?

Michael

[1] http://www.day.com/specs/jcr/2.0/24_Repository_Compliance.html#24.2%20Repository%20Descriptors