Status: New
Owner: [email protected]
New issue 718 by [email protected]: Misplaced annotation check may be
overly strict when dealing with legacy code
http://code.google.com/p/google-guice/issues/detail?id=718
This is not really a defect as such, and only affects a few scenarios, but
just wanted to capture the use-case.
When dealing with legacy code you may encounter interfaces with misplaced
annotations (such as @Singleton). They might use this as a kind of
extension-point documentation, or as a way to generate bindings at runtime.
Currently any use of such an interface in Guice will cause the injector to
throw a configuration error - the only way to avoid this is to use a
different interface or get the interface changed upstream. However
sometimes an upstream change is not possible, and it would be useful if
instead the injector could be configured to log such errors as warnings.
While this particular use-case is narrow, there may be other errors which
are technically not fatal and could be logged as warnings when running in
some sort of "non-strict"/"legacy" mode or stage.
--
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.
