Comment #53 on issue 62 by [email protected]: Lifecycle support http://code.google.com/p/google-guice/issues/detail?id=62
There's no need for the manager to call everything before anything is returned - we have a dependency graph, we can just call startup along the dependency chains.
Anyway, Jesse Wilson and I had a similar conversation about five weeks ago (I think) and came to a similar conclusion about an interface. I was working up a proposal, but hadn't seen this bug. I DO think it's important that we not go with the "start everything" approach. Too much up-front hit, I think. Wiring should happen up-front, but one point of separating out wiring from config from startup is to keep the costs of these pieces of work separate (and maintainable).
The other thing that needs to happen with any lifecycle system is a strong set of recommendations on where to do what kinds of work, so people have a clue. So much work is done in providers and constructors to-date, that having good instructions could ease migration to using the lifecycle in a maintainable and sane way.
-- You received this message because you are subscribed to the Google Groups "google-guice-dev" 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-dev?hl=en.
