Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

JCR Management

Revision as of 08:07, 24 June 2007 by Sandro.boehme.gmx.de (Talk | contribs) (To Do)

JCR Mangement (JCRM)

The Framework

It contains:

  • A reusable EMF resource implementation.
  • An extendable ecore model. It can be used by extending your domain entities from the JCRMNode entity in this model instead of EObject.
  • An extendable and lazy EStore implementation for operations on your model.

The JCR Manager

A tool that is based on top of the framework to use EMF, modeling projects and other projects to manage JCR content.

What works for the moment

  • Currently it displays the JCR content tree
  • It's possible to add nodes with a type defined in the domain model
  • It's possible to rename nodes
  • It's possible to remove nodes

The Contributions

  • Ed Merks helped as a mentor creating JCRM within Eclipse.
  • The ATL team contributed an initial meta model and transformation that will speed up ATL integration.
  • My employer inovex GmbH (http://www.inovex.de) contributes 5 person days where I can work on this project within working hours. Of course I'm eager to use this joker but I will need to find a time where I have no other important ToDo's at work.

To Do

  1. Implement JCRMStoreImpl.move() after the fix for the EMF Bug 194088 is available.
  2. Understand the Eclipse release engineering to know in which folder structure to check in the initial code.
  3. Submit a speach for the Eclipse Con Europe until end of june latest.

Next Milestone

Create a first downloadable presentation of the project to show the potential of Eclipse modeling to the Jackrabbit community.


Values

  • simplicity
  • transparency
  • no dependency on JCR implementations

Back to the top