This functionality was removed from Alfresco in 5.0.b.
Table of Contents
Release Date: May 1st, 2006
The first release will contain the basic features required to get the Alfresco JCR interface bound.
Basic binding class
The binding utility is the class which binds the JCR repository exposed by spring (Found in the Alfresco JCR module) with an RMI naming service.
Basic unit tests
Unit testing is a challenge because RMI requires a certain amount of infrastructure. We will look at providing some level of unit testing for this extention.
- JUnit Test - for inclusion is nightly builds, automated testing
- Console Application - test registration from the command line
- JSP Page - simple page to test from
Spring bean configuration
The binding utility is instantiated and managed by Spring.
Properties file based configuration
Implementation specific configuration will be located in a properties file. This configuration is not very user friendly but it is the basics. It can be overridden at the server level by putting a configuration file of the same name and path in the classpath.
The Alfresco JCR-RMI extention is a very basic Alfresco extention with a only a few moving parts, however we will attempt to provide as much documentation as we can.
Release Date: July 1st, 2006
The second release will focus on making the extention easier to use by providing a configuration and control panel for the binding utility. Configuration will be stored in the repository.
User updates RMI configuration (Server name, Server port, Binding name)
Unbind Alfresco JCR component from the RMI registry.
bind Alfresco JCR component in the RMI registry.