I'm taking a look at Guice to see how it would work for us, currently we code the IoC manually (giant main that wires everything up) and use factories to create dynamic objects so all methods are mock testable, i.e. no 'new' in the code (just in the main and factories).
I get how Guice solves the IoC part with @Inject & modules, however how does it help with the factories that generate dynamic objects? I.e. a method that calculates values, creates an object with those values, and does some work on and/or returns the object. How does Guice stop us from needing to write the class factory that generates the object? It looks like I could inject a typed Provider but that doesn't let me create the object with the values just created dynamically. (Also it would tie my code to the Guice APIs.) So it seems Guice solves the static part of the app but not the dynamic part or am I missing something? -- 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.
