Hi Massimo, You can also check out our integration with Spring Data: http://www.springsource.org/spring-data If you scroll down you can find links to the docs and the github repo.
This approach uses a simple POJO model with annotations, like JPA. It minimizes boilerplate code, and gives you a lot of stuff for free. There is also rudimentary cross-store support, for building applications that span across both a JPA datasource and Neo4j. Please let us know if you have any questions. David On Mon, Feb 14, 2011 at 6:56 AM, Massimo Lusetti <[email protected]> wrote: > Hi all, > In almost all applications/examples/doc/wiki I've seen on neo4j.org > the domain is based on POJO and this is somewhat usual but here I see > you suggesting doing interface for POJO. > > Having an Actor interface implemented by an ActorImpl classes which is > a POJO plus a reference to the "underlying node". > > First why having an interface declaring a POJO just for > getters/setters method, isn't this boilerplate code? > Second since you do that, why not exposing the "underlying node" as a > getter so you can just use Actor and never had to cast it to > ActorImpl? > > Am I missing something? > > Cheers > -- > Massimo > http://meridio.blogspot.com > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- David Montag Neo Technology, www.neotechnology.com Cell: 650.556.4411 [email protected] _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
