2010/2/4 Endre Stølsvik <[email protected]> > *My vote*, if it suddenly got tallied by someone, is firmly on the side of > letting the proxy-hell be configurable: For backward compatibility, let > Guice work as it does. But by setting some flag somewhere, Guice will NEVER > use proxies, and FAIL if there is any circularity. > > *I even believe Bob is with me on this one. :-)* >
Sorry we haven't fixed this yet. It will be addressed in two ways: 1) Inject all constructors first, and then setters. Right now we inject setters immediately after the constructor, so you can't use them to break circular deps. This is already in our issue tracker: http://code.google.com/p/google-guice/issues/detail?id=220&q=setter&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Extension 2) Detect circular deps statically. http://code.google.com/p/google-guice/issues/detail?id=296&q=circular&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Extension We'll definitely make the proxies an opt-in feature at some point. Bad experiment. Bob -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
