JSR-170 Compliance

From AlfrescoWiki

Back to JSR-170

Contents 1 Introduction 2 Level 2 Compliance (from Alfresco v1.2) 2.1 Current Issues / Incompatibilities 2.1.1 setProperty(java.lang.String name, Value[] values, ...) 2.1.2 Storing Binary in an ANY Type 2.1.3 Multiple Workspaces not supported 3 Level 1 Compliance (Available in Alfresco v1.0) 3.1 TCK Results

[edit] Introduction

This page tracks our compliance with JSR-170.

[edit] Level 2 Compliance (from Alfresco v1.2)

[edit] Current Issues / Incompatibilities

[edit] setProperty(java.lang.String name, Value[] values, ...)

From the JSR-170 specification...

All Value objects in the array must be of the same type, otherwise a ValueFormatException is thrown. If the property is not multi-valued then a ValueFormatException is also thrown. If another error occurs, a RepositoryException is thrown.

We don't currently throw the exception, instead, we cast the values to the required type.

[edit] Storing Binary in an ANY Type

This is not currently supported in Alfresco.

[edit] Multiple Workspaces not supported

This is not currently supported via the JCR API - therefore methods such as:

1. workspace.copy(java.lang.String srcWorkspace, java.lang.String srcAbsPath, java.lang.String destAbsPath)
2. workspace.clone(...)

are not implemented.

[edit] Level 1 Compliance (Available in Alfresco v1.0)

We pass all Level 1 TCK tests.

Whilst testing our Repository against the JCR TCK, we found some issues with the tests themselves. The good news is that they've been reported to the Jackrabbit development team and all have been promptly fixed. Thanks.

[edit] TCK Results

Image to be updated...