Comment #114 on issue 62 by [email protected]: Lifecycle support
http://code.google.com/p/google-guice/issues/detail?id=62
GIN only uses Guice at compile time, so additional work is required to
support extensions - for example, assistedinject and multibinder have both
been adapted in GIN (but the API/design is based on the original
extension). See the various submodules under
http://code.google.com/p/google-gin/source/browse/#svn%2Ftrunk%2Fsrc%2Fcom%2Fgoogle%2Fgwt%2Finject%2Fclient
So while the API and code to support lifecycles is available, it will need
to be adapted for GIN. Whether this is done by porting and re-implementing
the underlying TypeListener/ProvisionListener API on top of GIN's GWT
runtime, or by looking at lifegycle's higher-level design and porting that,
is a question for the GIN folks.
(PS. the original home for lifegycle was http://99soft.github.io/lifegycle/
before it moved to Apache/Onami)
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
