On Sun, Feb 20, 2011 at 8:20 PM, Michael Hunger <michael.hun...@neotechnology.com> wrote: > all finders map back to the underlying graph so it doesnt matter which one to > use. > > one could still add a toVertex wrapper to your domain objects to have them be > usable in tinkerpop > > what is the usecase you want to achieve with the combination of spring data > graph and tinkerpop > So far I'm just experimenting with different ways query the graph :-) In the end I hope to build an "AbstractRepository<T>" class that would allow me to find things in the same underlying graph using TraversalDescriptions, Pipes, Gremlin or even SPARQL. Having that would add a lot of flexibility in writing domain methods.
> glad that spring data graph works well for you if you have any feedback or > issues just ping me Yes. Spring data is very interesting. Although I am still trying to understand how to query a graph of heterogeneous nodes and relationships and discover patterns. A quick/trick question: I noticed that father.relateTo(child, RelationshipTypes.PARENT) works only if father has Direction.BOTH or Direction.OUTGOING; and @RelatedTo(type = "PARENT", elementClass = Person.class, direction = Direction.INCOMING) private Set<Person> children; .... father.relateTo(child, RelationshipTypes.PARENT); .... father.getChildren() would return empty in case of Direction.INCOMING this might be confusing! Thanks, Alfredas _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
