资 源 简 介
Notice: This project currently leads to annotation hell. I am thinking of reimplementing this using fluent interfaces from a superclass, or / and moving it to scala.
A mapper that maps objects to a Neo4j graph, like an object-relational mapper maps objects to a relational database. But there are some differences:
This mapper offers more than traditional orms since it uses neo4j underlying graph to manage relationships for you: When your entities have a parent-child relationship, adding a child to the parent automatically sets the parent in the child.
Instead of the traditional load-store cycle normally used in mapping, the ogrm approach is to intercept calls to the entities and synchronize the entity with the underlying storage mechanism right away. This is possible since neo4j is running in process, and its caching mechanism makes it seem like the underlying data is in memory all the time.
