New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The framework can handle the lifecyle of the service #3

Closed

minjing opened this issue May 12, 2015 · 0 comments

Assignees

Labels

Milestone

Owner

minjing commented May 12, 2015

Normally the service has a lifecycle: resolved, satisfied, initialized, destroyed.

Resolved: the service is resolved, but all dependencies is not set, the service can't serve.
Satisfied: all dependents has been set to the service,
Initialized: the initialization method of the service has been invoked, the service can serve to outside.
Destroyed: the service has been destroyed.

minjing added the enhancement label

minjing added this to the M1 milestone

minjing self-assigned this

minjing closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment