weld00148 - unsatisfied dependencies.

[jdelgadot]

Hi,

I am working in a project with cdi-vaadin.

i replayed de tutorial vaadin-cdi

https://vaadin.com/wiki?p_p_id=36&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=row-1&p_p_col_pos=2&p_p_col_count=4&_36_struts_action=%2Fwiki%2Fview&p_r_p_185834411_nodeName=vaadin.com+wiki&p_r_p_185834411_title=II+-+Injection+and+scopes

It has only a :

public interface Greeting {

  public String getText();

}

public class SimpleGreetingImpl implements Greeting, Serializable {

  @Override

  public String getText() {

  return "Hello, World!";

  }

}

The inject point is in the UI of Vaadin.

@SuppressWarnings("serial")

@CDIUI("")

@Theme("valo")

public class HelloWorldUI extends UI {

  @Inject

  private Greeting greeting;

...

When i tried to deploy i ve got the ERROR

WELD-001408: Unsatisfied dependencies for type Greeting with qualifiers @Default

In the Eclipse IDE I've got a warning in the injection point

No bean is elegible to the injection point [JSR-346 5.2.2]

In JSR-346 5.2.2 talk that an unsatisfied dependency exist at an injection point when no bean is elegible for injection to the injection point.

I have an implementation of greeting, why the container can't see it?

[nickarls]

The most classic mistake is missing a beans.xml

[tremes]

Yes if you are deploying to WildFly and you don't have beans.xml in your app then the default discovery mode is annotated. See implicit bean archive section at Weld 2.3.4.Final - CDI Reference Implementation or Contexts and Dependency Injection for the Java EE platform. Another option is to put some bean defining anotation at SimpleGreetingImpl

[jdelgadot]

By default the bean.xml file that created Eclipse is with annotated bean discovery mode (so this is an implicit bean archive).

But if i change to all bean-discovery-mode it will be a explicit bean archive?

I am not sure what is the difference.

Explicity needs to write the beans in the archive?

[tremes]

Well yes this section in the spec is really bit confusing. Implicit bean archive is considered as an archive without beans.xml and with some bean defining annotations. What matters is the difference between "annotated" and "all" bean discovery modes. If you change it to "all" then you will really have explicit bean archive but as I said in previous sentence.:-)