About the CORM Project

CORM is an acronym for Commercial Object Relational Mappings. The project's goal is twofold:

1. Implement commercial archetype patterns in Java.
2. Define object relational mappings to a persistent data store using Open Source Java Data Object technologies.

In real life, a corm is a swollen underground stem that serves as a storage organ to enable the plant to survive winter and other tough conditions. That's sort of what we expect a persistence mechanism to do in software development, as well, so at least the acronym's not a complete loss.

The CORM project was inspired by a book on business archetypes in the summer of 2004. Alex Saint Croix originally wanted to develop the software for a CMS project he was working on for a company in Minneapolis, Minnesota. At the time, JDO 2.0 was still just a twinkle in many people's eyes and after finding he couldn't easily implement the software in version 1.0 of JPOX, Alex shelved it and moved on to other work.

Alex came back to CORM in December of 2005 and made major inroads until he realized that the Rule Archetype Pattern presented in the Neustadt-Arlow book was not adequate for production. He turned his attention to finishing a working version of his Arete Rule Engine.

This August Alex completed major milestones in his rule engine development, and has since returned his attention to CORM while learning the basics of Solaris administration. The addition in mid-October of a real Subversion-powered development server has launched CORM back into full gear, and attracted the project's second developer, Catharine Tierney. Catharine will be working on developing unit tests and providing much needed quality assurance and API documentation in the coming months.

News

• (10.28.2007) CORM Alpha 02 Release Available for Download! See the CORM Downloads page for details
• Announcement of the Commercial Object Relational Mappings project