multiple @Produces for same return type

[gonorrhea]

Ok, so I'm a newbie here (I wish there was a Seam --> Web Beans transition book).

Consider the following from the Web Beans spec:

@SessionScoped @Model
public class Login {
@Produces @LoggedIn User getCurrentUser() {
if (user==null) {
throw new NotLoggedInException();
}
else {
return user;
}
}

@Model
public class DocumentEditor {
@Current Document document;
@LoggedIn User user;
@PersistenceContext EntityManager docDatabase;
...
}

Ok, so what happens if there is another Web Bean component, that has the following method:

@Produces @LoggedIn User getMyUser() {...}

So which method will get called by the Web Beans manager?

As per spec:

The method annotated @Produces is a producer method, which
will be called whenever another Web Bean in the system needs the currently logged-in user.

[dan.j.allen]

You'll get an error at startup. That's the whole point of Web Beans. It is deterministic.

[gonorrhea]

aha, so similar to what happens in a Seam app when you have more than one Seam component annotated with @Name("foo")

[nickarls]

Yep. You can get some overlapping by using deployment types but even then there is an enabled order in configuration.

The everything is a Bean does have some implications in inheritance when you have a class Foo that extends Bar that extends Tar and inject for API type Tar and get hit with ambiguous resolves.