eXo Java Content Repository and ECM 1.0 Released
- Share
-
- |
Read later
Reading List
Exo and Objectweb have announced the release of their Java Content Repository JCR 1.0 open source product (an implementation of JSR 170) as well as ECM (Enterprise Content Management) 1.0 tools, part of the eXo portal platform which also includes a JSR 168 compliant portal server.
The eXo JCR 1.0 is an implementation of the JSR 170 specification that includes all the required functionalities (level 1, 2 and all optional features) such as document definition, searching capabilities, import/export functionalities, locking, versioning and many more. The default implementation is based on a relational database implementation and has been tested on major products such as Oracle, DB2, SQLServer, MySQL. It supports XA transactions.
The eXo ECM 1.0 provides tools on top of the Portal and JCR content store to enable more document management functionalities such as WebDAV interaction, Publication Validation Workflow with delegation support, document backup, and a template mechanism to create and visualize structured documents. The new 'Action' concept allows Business Process, Drools Rules or Groovy Scripts to be launched or executed when documents are read, added or removed from a dedicated JCR workspace.
eXo Platform joined ObjectWeb's open source portfolio in November 2004. Exo also includes a JSR 168 compliant portal server. The new eXo JCR and ECM projects are already being used in production on Italy's Venice District news portal InfoQ also runs on a JSR 170 repository (Apache Jackrabbit/Magnolia).
3
Discuss
The eXo JCR 1.0 is an implementation of the JSR 170 specification that includes all the required functionalities (level 1, 2 and all optional features) such as document definition, searching capabilities, import/export functionalities, locking, versioning and many more. The default implementation is based on a relational database implementation and has been tested on major products such as Oracle, DB2, SQLServer, MySQL. It supports XA transactions.
The eXo ECM 1.0 provides tools on top of the Portal and JCR content store to enable more document management functionalities such as WebDAV interaction, Publication Validation Workflow with delegation support, document backup, and a template mechanism to create and visualize structured documents. The new 'Action' concept allows Business Process, Drools Rules or Groovy Scripts to be launched or executed when documents are read, added or removed from a dedicated JCR workspace.
eXo Platform joined ObjectWeb's open source portfolio in November 2004. Exo also includes a JSR 168 compliant portal server. The new eXo JCR and ECM projects are already being used in production on Italy's Venice District news portal InfoQ also runs on a JSR 170 repository (Apache Jackrabbit/Magnolia).
Rate this Article
- Editor Review
- Chief Editor Action
Submit
Submit
Hello stranger!
You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think
Community comments
great to see a new JCR implementation
by
Alex Popescu
Posted
Re: great to see a new JCR implementation
by
Floyd Marinescu
Posted
Re: great to see a new JCR implementation
by
Alex Popescu
Posted
great to see a new JCR implementation
by
Alex Popescu
It is great to see a new open source JCR implementation, though I haven't been able to find a reference about the licensing of the eXo JCR implementation. However, congrats! I am sure I will check it soon ;-].
./alex
--
.w( the_mindstorm )p.
./alex
--
.w( the_mindstorm )p.
Re: great to see a new JCR implementation
by
Floyd Marinescu
I'm very curious about what a side by side comparison between the different JCR's available on the market might look like.
Floyd
Floyd
Re: great to see a new JCR implementation
by
Alex Popescu
As far as I know, at this moment there would be 4 JCR implementations available: Jackrabbit, CRX, eXo and Alfredo. What kind of comparison do you have in mind?
./alex
--
.w( the_mindstorm )p.
./alex
--
.w( the_mindstorm )p.
