WELD-001408: Unsatisfied dependencies when moving @Produces method to a different module

[jenskoefod]

Hi, I'm a beginner with CDI so I'm probably overlooking something obvious.

I have a qualifier annotation and an @Produces method to inject system properties into fields in an EJB implemetation. When these classes are in the same EAR/jar as the injection itself it works, but when I move it to a separate EAR (so I can use it from all EARs) I get the following error:

WELD-001408 Unsatisfied dependencies for type [String] with qualifiers [@Config] at injection point [[field] @Config @Inject private com.one.myappl.ejb.session.myappl.MyFacadeEJB.serverInMails]

Both the defineing jar (shared-utils.ear/common-utils.jar) and the EJB implementation (myappl.ear/myappl-ejb-impl.jar) contain beans.xml with only the root element.

jboss-deployment-structure.xml in myappl.ear declares a dependency on shared-utils:

<jboss-deployment-structure>
  <ear-subdeployments-isolated>true</ear-subdeployments-isolated>
  <deployment>
    <dependencies>
      <module name="deployment.sharedutils.ear" export="true" />
      ...

Here is the simplified code

// Config.java in shared-utils.ear/common-utils.jar
@Qualifier
@Target({FIELD})
@Retention(RUNTIME)
public @interface Config {
}

// ConfigurationFactory.java in shared-utils.ear/common-uils.jar
public class ConfigurationFactory {
    public @Produces @Config String getStringConfiguration(InjectionPoint p) {
        return "myserver"; // Should look up the system property based on p
    }
}

// Facade class in myappl.ear/myappl-ejb-impl.jar
@Stateless
public class MyFacadeEJB implements MyFacade {
    
    @Inject @Config
    private String serverInMails;
...

[jerome110011]

Hello Jens,

I've got the exact problem like you. The only difference is that I deploy my projects one for one.

I posted my problem on SO: http://stackoverflow.com/questions/23733540/cdi-2-projects-inject-weld-001408-error/23754016#23754016

You could try to place the beans.xml in different places. And to use the @Named annotation. Thats all I know

[mkouba]

Hi Jens,

your deployment scenario is a bit uncommon and definitely not portable accross Java EE containers. I don't think it's a good idea to have "sharedutils.ear", instead I would create a simple "sharedutils.jar" and place it in each EAR lib directory.