Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JCR Management"
(→The Contributions) |
(→What works for the moment) |
||
Line 13: | Line 13: | ||
* It's possible to remove nodes | * It's possible to remove nodes | ||
* It's possible to rename nodes | * It's possible to rename nodes | ||
+ | |||
== The Contributions == | == The Contributions == | ||
* Ed Merks helped as a mentor creating JCRM within Eclipse. | * Ed Merks helped as a mentor creating JCRM within Eclipse. |
Revision as of 18:59, 15 June 2007
Contents
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
- It's possible to add nodes
- It's possible to remove nodes
- It's possible to rename nodes
The Contributions
- Ed Merks helped as a mentor creating JCRM within Eclipse.
- The ATL team contributed an initial meta model and transformation to 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.
To Do
- Try to reproduce why my move() method is not called
- Get the generated editor to call my EStore methods. It will probably not work out of the box with the generated commands of Edit-Framework.
- Understand the Eclipse release engineering to know in which folder structure to check in the initial code.
- 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