Comment #58 on issue 62 by sberlin: Lifecycle support http://code.google.com/p/google-guice/issues/detail?id=62
@dhanji -- So long as multiple .start() calls are ignored (the service isn't started twice), and the returned Future from latter calls still works for blocking.. that seems like a good plan. I'm a little scared about having an insanely large CompositeService -- kind of like an additional Module, except for service ordering instead of object wiring.
@cwg -- It's often the case that a service has no need for a real "wiring" dependency on something else, but it still has a service dependency on it. It would be ashame, I think, to force an object dependency on it. This has been what's nice about Guice not including lifecycle as part of a base feature -- it separates lifecycle dependencies from object dependencies.
-- 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.
