From ron.gross on October 07, 2010 02:47:36

(Using Guice version 2.0)

From ron.gross on October 07, 2010 02:56:00

A few workarounds that I've found:

1. Using a Provider instead of Guice's Proxy seems to resolve the issue.
2. When using asEagerSingleton the problem does not reproduce.

Is there a way to disable the proxy generation for circular dependencies (make it thorw an exception)? I would rather always use a Provider instead of a proxy until this is fixed, and would like an easy way to catch all these cases where my code has circular dependencies.

From ron.gross on October 07, 2010 04:51:41

Also - the problem does not reproduce if I don't bind the objects as singletons.

From sberlin on October 07, 2010 05:21:12

Re: Is there a way to disable the proxy generation for circular dependencies (make it throw an exception)?

Yes, but it requires Guice 3.0 (or more specifically, the code in SVN since 3.0 is not released yet).  Use InjectorBuilder.disableCircularProxies.

From ron.gross on October 07, 2010 06:05:03

I actually tried that, but I see that some tests are failing in trunk, and also had problems compiling my code against Guice 3.0. For now I resorted to making the classes non-singletons.

From sberlin on October 07, 2010 06:43:15

The AllTests target suppresses some tests that are known to fail (they're written against expectations that Guice doesn't fulfill yet).

What issues are you seeing compiling against 3.0?  It should be a trivial swap.

This issue seems over 5 yrs old. Was there a solution, is there a new version of Guice that has adressed this ?

We get this issue at runtime not in compilation.

The exception is expected. If you have circular dependencies and use the circular dependencies before they're initialized, you will get an exception. You can use Binder.disableCircularProxies to disable the circular proxy feature of Guice. This was released in Guice 3.0, ~5 years ago.