Comment #56 on issue 62 by [email protected]: Lifecycle support http://code.google.com/p/google-guice/issues/detail?id=62
Why would Foo not have guice visible dependency on Bar/Baz, if Guice is actually creating the wiring graph... I don't mean it has to have a direct visible dep on Bar or Baz, but it should have a sort of transitive dependency on those that Guice, having wired up the graph first, knows about.
Picocontainer does it this way and it works nicely. Components which need lifecycle implement the start() semantics, and the container starts them in dependency order as-needed. What am I missing about how Guice handles things? Or is the lifecycle proposal external to the Injector entirely?
-- 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.
