jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Stocker <christian.stoc...@liip.ch>
Subject Re: [jr3 optional features]
Date Thu, 23 Feb 2012 06:47:45 GMT
Hi

On 22.02.12 19:31, Michael Dürig wrote:
> 
> 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.
[..]


> node.type.management.orderable.child.nodes.supported = false

Why no orderable child nodes? We started using that for a project and if
that's going away in the long term, we maybe start finding other
solutions now :)

chregu

> 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
> 

Mime
View raw message