Comment #115 on issue 62 by [email protected]: Lifecycle support
http://code.google.com/p/google-guice/issues/detail?id=62
Bob,
In comment #93 you said "Maybe I don't want the object to be closed." When
I asked you for a concrete use-case you responded with some general
statement about avoiding unexpected behavior.
1. Do you have a *concrete* use-case where you wouldn't want to close() at
the end of a scope? You asked me for a concrete use-case where you would
want to do so, and I have provided one.
2. In my view, we're not doing anything unexpected... certainly no more
than closing resources at the end of a try-with-resources block. This
behavior should be baked into the specification of what it means to be a
Scope. Just to clarify: I am implying that request-scoped resources get
disposed at the end of the request, but singleton-scoped resources do not.
Meaning, we do not close() inherited bindings.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice-dev.
For more options, visit https://groups.google.com/groups/opt_out.
