Issue 65 in project google-guice

[codesite...@google.com]

Issue 65: Run code after injection
http://code.google.com/p/google-guice/issues/detail?id=65

New issue report by crazyboblee:
We need to be able to run code after construction and before scoping. For
example, Struts 2 interceptors need init() called, and they need
configuration properties set.

Issue attributes:
Status: Accepted
Owner: crazyboblee
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 65: Run code after injection
http://code.google.com/p/google-guice/issues/detail?id=65

Comment #1 by h...@formicary.net:
This ties into http://code.google.com/p/google-guice/issues/detail?id=62&can=2&q=&sort=-id

My vote would be to go with the standard approach and allow a @PostConstruct annotation.

[codesite...@google.com]

Issue 65: Run code after injection
http://code.google.com/p/google-guice/issues/detail?id=65

Comment #2 by crazyboblee:
@PostConstruct (or @PostInject :)) works for code in the class, but we should also
support external logic, kind of like Spring's post processors.

Issue attribute updates:
Status: New
Labels: -Type-Defect Type-Enhancement

[codesite...@google.com]

Issue 65: Run code after injection
http://code.google.com/p/google-guice/issues/detail?id=65

Comment #3 by james.strachan:
Sounds good to me; allowing folks to post process in other ways (e.g. to support
other kinds of annotation or APIs like Spring's InitializingBean etc).

[codesite...@google.com]

Issue 65: Run code after injection
http://code.google.com/p/google-guice/issues/detail?id=65

Comment #4 by kevinb9n:
This describes Provider Interceptors, issue 78, in a nutshell.

Issue attribute updates:
Status: Duplicate