It should use the factory methods in TraversalFactory instead.

How come we exposed DefaultExpander to begin with? Wasn't that class just
supposed to be an implementation detail?

The fact that it had the weird behavior of expanding all RelationshipTypes
when it was empty turns on the "implementation detail" warning light for me.

I'm working on refactoring the new traversal framework, so expect things to
change (and break) more. It's good that you report this though, since
examples should be updated to match the "best practices". The new traversal
API is after all not stable yet (since 1.1 has not been released), but
I apologize for the inconvenience anyhow.


On Wed, Jun 23, 2010 at 9:21 AM, Paddy <> wrote:

> Hi,
> was removed from the latest build
> How can i get the example from github working without the DefaultExpander ?
> DefaultExpander relExpander = new DefaultExpander();
> relExpander.add( RelationshipTypes.ROAD, Direction.BOTH );
> AStar sp = new AStar( graphDb, relExpander, costEval, estimateEval );
> Path path = sp.findSinglePath( NYC.getUnderlyingNode(),
>  SF.getUnderlyingNode() );
> thanks
> Paddy
> _______________________________________________
> Neo4j mailing list

Tobias Ivarsson <>
Hacker, Neo Technology
Cellphone: +46 706 534857
Neo4j mailing list

Reply via email to