Okay I'm new to Guice so maybe I'm missing something but since I converted one app to use Guice I've found some things that I just don't like, I'm wondering if folks have found solutions or have suggestions.
1. No IDE help. I use IDEA and as of yet it is not Guice aware so all my refactoring/code support is broke. And I have to build the modules by hand which is just as hard as making the factory manually before I used Guice. So to me Guice just moves the problem around. At least when I made manual factories the IDE could keep changes in sync. 2. Loss of compile time checking. Just by running the compiler I can't tell if my code is complete, by that I mean have all the right modules/parameters, I don't find out something is wrong until runtime. Prior to this, using manual factories, this was a given. Perhaps I need to add a unit test that forces Guice to create an instance of the class so it least I could know during the test phase that the module/factory is correct? 3. Can't keep track of all the modules. As best I can tell nothing in the module code even says what class it's a factory for. There is too much annotation magic going on, apparently @Inject is enough for Guice to 'know' that someplace in vast numbers of Guice modules there should be one that has the right mix of input parameters? What am I doing wrong? I feel like this is a couple steps in the wrong direction. -- 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.
