Hi there, so the problem is solved for you? If you have more questions, maybe you can post a GIST so I can have a look?
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - NOSQL for the Enterprise. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. On Mon, Oct 24, 2011 at 9:12 AM, Rubicon <[email protected]> wrote: > Realized, that I've to give the hole path to the node I'm looking fore... > have: > [refNode]----USER--->[user]----HAS_OCCUPATION---->[occupation] > For some reason the traverser > Traverser usersTraverser = firstNode.traverse(Order.BREADTH_FIRST, > StopEvaluator.END_OF_GRAPH, > ReturnableEvaluator.ALL_BUT_START_NODE, > RelTypes.HAS_OCCUPATION, Direction.OUTGOING); > wouldn't find the [occupation] node. Adding additional parameters to the > traverser (RelTypes.USER, Direction.OUTGOING), and implementing the > ReturnableEvaluator to return > currentPosition.lastRelationshipTraversed().isType(RelTypes.HAS_OCCUPATION) > have done the job. > Don't have to commit the transaction also. > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Traversing-graph-after-adding-node-tp3448023p3448255.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
