Guice best practices and anti-patterns

Question

I'm not sure if there is merit to this question or not, but are there any best practices and anti-patterns specific to Google Guice?

Please direct any generic DI patterns to this question.

I'd encourage anyone interested in contributing to this question to check out the [Guice docs](http://stackoverflow.com/documentation/guice/topics) topics instead. — dimo414, Feb 08 '17 at 00:35

score 31 · Answer 1 · answered Nov 08 '09 at 20:58

31

I have always felt that constructor injection to final fields is a best practice. It minimizes mutable state and makes the class easier to understand by making the class's formal dependencies explicit.

public class MyClass {
    private final MyDependency dependency;

    @Inject
    public MyClass(MyDependency dependency) {
        this.dependency = dependency;
    }
}

answered Nov 08 '09 at 20:58

SamBeran

1,944
2
17
24

What if We have dozens of dependencies? The constructor would be terrible – jilen Aug 28 '13 at 03:32
12

having dozens of dependencies on a single class is probably a good indication that the class is responsible for too much and should be refactored. – Matthew Madson Sep 12 '13 at 01:59
If you expect to write a unit test then this is definitely the way to go! – Kurru Jul 24 '14 at 19:06

score 14 · Answer 2 · edited Apr 20 '15 at 09:38

14

There are some on the Guice project page. Here's a link to the first one, and you can see the others in the sidebar.

That said, I think it would be great to see others posted and voted on here. Then we can write the best of them up for the Guice pages.

edited Apr 20 '15 at 09:38

Jonathan

20,053
6
63
70

answered Nov 05 '09 at 21:39

Kevin Bourrillion

40,336
12
74
87

Guice best practices and anti-patterns

2 Answers2

Linked