Comments on: Using Google Guice Providers to Solve Law of Demeter Problems http://codemonkeyism.com/using-google-guice-providers-to-solve-law-of-demeter-problems/ Fri, 30 Jul 2010 06:49:07 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: stephan http://codemonkeyism.com/using-google-guice-providers-to-solve-law-of-demeter-problems/comment-page-1/#comment-135733 stephan Thu, 24 Jul 2008 19:25:54 +0000 http://stephan.reposita.org/archives/2008/07/24/using-google-guice-providers-to-solve-law-of-demeter-problems/#comment-135733 @Doug: Of course you're right, my error, passing in <code>Context</code> is IoC. "Sometimes that’s not possible. With IoC this can be solved without (much) refactoring." Reading my post again, I didn't write that passing in a Context is not IoC, just that IoC can solve the problem. @Doug: Of course you’re right, my error, passing in Context is IoC.

“Sometimes that’s not possible. With IoC this can be solved without (much) refactoring.”

Reading my post again, I didn’t write that passing in a Context is not IoC, just that IoC can solve the problem.

]]> By: Doug http://codemonkeyism.com/using-google-guice-providers-to-solve-law-of-demeter-problems/comment-page-1/#comment-135662 Doug Thu, 24 Jul 2008 16:25:41 +0000 http://stephan.reposita.org/archives/2008/07/24/using-google-guice-providers-to-solve-law-of-demeter-problems/#comment-135662 To be picky about terminology, passing a Context object IS a form of IoC. It's what used to be called "Type 1" IoC, or "Contextualized Dependency Lookup". It's not Dependency Injection, but it IS Inversion of Control. (One could argue that the dependency on the injected context qualifies as DI, but I don't think that argument would win many supporters.) As noted, it's harder to test than DI is. As for the Law of Demeter, I say "ptthht." There are some places where it's a reasonable guideline, and many places where it isn't. The real problem with passing a Context object instead of an Engine object is one of increased coupling: the method is not only coupled to the Engine class but to the Context class as well. To be picky about terminology, passing a Context object IS a form of IoC. It’s what used to be called “Type 1″ IoC, or “Contextualized Dependency Lookup”. It’s not Dependency Injection, but it IS Inversion of Control. (One could argue that the dependency on the injected context qualifies as DI, but I don’t think that argument would win many supporters.) As noted, it’s harder to test than DI is.

As for the Law of Demeter, I say “ptthht.” There are some places where it’s a reasonable guideline, and many places where it isn’t. The real problem with passing a Context object instead of an Engine object is one of increased coupling: the method is not only coupled to the Engine class but to the Context class as well.

]]>