From crazyboblee on March 07, 2007 14:32:03

That should read, "right now, we match injection points to bindings using only the
exact type."

From bslesinsky on July 07, 2007 17:32:00

Maybe the module could ask for this:

  bindAllSuperTypes().to(FooImpl.class).
 
...but with a less ugly name.

But I could see this getting banned by some style guides for similar reasons as
wildcard imports.

From limpbizkit on May 30, 2008 00:39:03

If the type hierarchy is this:
   class UserImpl implements User
   interface User implements Entity, Serializable, Identity
...it's very difficult to automagically decide which types UserImpl should satisfy. The best I can recommend is that
users write their own utility methods. Perhaps one of these:
  bindImplementedInterfaces(UserImpl.class);
  link(UserImpl.class, User.class, Identity.class);

Status: New
Labels: -Priority-Medium Priority-Low

From sven.linstaedt on June 16, 2008 10:24:05

-1 for suggestion #1
because of the mentioned complexity

+1 for suggestion #2
because it saves us from configuring a lot bindings. Even @SessionScoped might be a
binding and a scope annotation, you have to configure each bean for each scope in
order to archive differently scoped injections for the same bean type. The map of
scopeAnnotation->scope does already configured, so its "only" a matter of applying
the annotated scope of a dependency to it's binding's provider. Open questions: Is
the currently configured scope for that binding replaced or is the configured scope
enclosed in the annotated one?

From sberlin on May 02, 2010 05:52:17

Moves Guice a bit too far into the classpath-scanning land.  It would be pretty easy
for an extension to support this, by including some kind of new bindAllSupertypes()
method and scanning the classpath for supertypes.  If folks sufficiently want it,
that extension will pop up and be used.

Status: WontFix