Hi, I think my first post was deleted earlier, so this is an attempt to rephrase it.
Where in the dependency injection chain should I be making calls to a database (SQLite) for storing and recalling a large set of values from any and every object in the graph. Many classes store one or more values and usually have their own settings object with many values that plug into the constructor. Modules also plugin to most of these objects at some point to provide different implementations for getting needed values from the database. Is this a problem that is best started at the database object and then given the data it needs through constructor parameter inputs the build the full graph? Is it possible to have the abstract structure at the bottom and the database access further up? Every object has maybe 1-10 settings to different tables and there are hundreds of thousands of objects and hundreds of classes. I am a music composer by profession. I rely on the software I make and I am constantly expanding it. Currently its in a archaic pre- functional language and I am trying to refactor it to dependency injection so that I can benefit from the expandability and testability that I have been desperately needing. I really like the DI approach, but I am having trouble with the database aspect. Thanks, Casey -- 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.
