Java API Reference

CRX 2.0 is a major product release, supporting the new release of JCR API version 2.0. As such, it gives a good opportunity to clean up the code base from very old and inefficient modules to give a clean slate for strategic product development.

A lot of functionalities have also been implemented in the reference implementation of the JCR standard, Apache Jackrabbit, which is used by CRX as the repository core. Some of the modules (e.g., repository filesystems) are now available directly in Jackrabbit, and they should be used in product configurations instead of the older CRX-side modules.

Deprecated in CRX 2.0:

• com.day.crx.i18n.CRXTranslationProvider and LanguageManager are not instantiated any more, and are obsolete. Use Sling for i18n support in applications.
• NativePersistenceManager is marked as obsolete and will be removed in future versions
  

Removed in 2.0:

• CQFileSystem was replaced by bundle persistence and TarPM. In case you are using this in any configuration, or have bundle/item persistence with blobFSBlockSize or itemFSBlockSize greater than zero, please migrate the configuration to use the newer features
• Removed obsolete persistence managers. Please use TarPM or BundleDB persistence managers with the supported databases (Oracle, MS SQL, DB2, MySQL):
  
  • JDBMPersistenceManager
  • persistence managers based on SimpleDbPersitenceManager
  • persistence managersbased on DbPersistenceManager
  • some of the Bundle persistence managers not recommended for Day products - BundleFsPersistenceManager, DerbyPersistenceManager, H2PersistenceManager
• Database filesytem (com.day.crx.core.fs.db package) has been removed; please use the corresponding classes from Apache Jackrabbit in your configurations instead (org.apache.jackrabbit.core.fs.db.*). Note that most of the CRX-side classes were just exending the corresponding Jackrabbit class.
  
  • If you use EmbeddedHSQLDbFileSystem, please contact Day for advice.
• Deprecated crx nodetype classes
  
• Security APIs have been standardized in JCR 2.0 and / or provided to a large extend in the reference JCR implementation, Apache Jackrabbit 2.0. The old, proprietary security module in CRX has been therefore removed and CQ5.3 and CRX 2.0 products adapted to the standards-based implementation (see below).

With the introduction of JCR 2.0 standard, and the release of Jackrabbit 2.0 implementing this standard, the following important improvements have been introduced in the area of security (permission and principal management):

• JCR 2.0: standardized the Access Control Management in the areas of privilege discovery and assignment of access control policies (API documentation: the new javax.jcr.security package).
  
• Jackrabbit 2.0: implements the newly standardized access control management, and provides its own implementation of user/group management (API documentation: the org.apache.jackrabbit.api.security and org.apache.jakcrabbit.core.security packages).
• Jacrkabbit 2.0: provides an implementation of an access manager, which uses the new JCR standard and Jackrabbit security features. (API documentation: the new org.apache.jackrabbit.core.security.DefaultAccessManager).

This set of JCR- and community-standardized security services for the content repository allowed for their adoption in Day Products (CQ WCM, DAM, Social Collaboration) and replacement for the previous, Day proprietary solution. The following changes have been introduced:

• CQ and CRX security / user management related user interfaces have been adapted to use the new APIs
• Security-related modules (like LDAP integration) has been adapted to use the new APIs
• The older CRX security module has been removed
• The security content (user/group/ACLs) in pre-2.0 repositories is automatically migrated while upgrading to CRX 2.0
• The crx.system workspace has been removed (user/group information is no longer stored there)
• The user/group information is managed under /home node for each workspace

See the respective security APIs and CQ 5.3 upgrade documentation for more details.

As of version 1.4, CRX supports three client-level API interfaces: the standard JCR 1.0 API, the Jackrabbit extensions in jackrabbit-api, and the CRX extensions in crx-api. Full compatibility with Jackrabbit has been added in this release (see section Jackrabbit Compatibility), and Jackrabbit APIs can be used with CRX directly.

The implementation of all these interfaces is fully backwards compatible with two changes in the CRX API described below.

1. The following methods have been removed from the crx-api extension interfaces:

• Package com.day.crx: CRXSession.getNamespaceResolver()
• Package com.day.crx.nodetype: NodeTypeRegistry.getRegisteredNodeTypes()

2. Any clients using the previous methods must be updated as follows:

• Use new SessionNamespaceResolver(session) instead of session.getNamespaceResolver()
• Use registry.getRegisteredNodeTypeQNames()instead of registry.getRegisteredNodeTypes()