Jar 从焊接中的另一个罐子中注入豆子

我有两个罐子A和B，其中A依赖于B

Jar B只有一个类：

@ApplicationScoped
公共类MyManagedBean{
私有字符串用户；
公共MyManagedBean（）{
//CDI所需的构造函数
}
@注入
公共MyManagedBean（@Named（“user”）字符串用户）{
this.user=用户；
}
...
}

JARA（更准确地说，EJB Jar）有一个bean：

@ApplicationScoped
公共类AnotherManagedBean{
公共AnotherManagedBean（）{
//CDI所需的构造函数
}
@注入
公共AnotherManagedBean（MyManagedBean）{
...
}
}

以及一个带有@products方法的配置bean：

@ApplicationScoped
公共类配置bean{
公共配置bean（）{
//CDI所需的构造函数
}
@产生
@命名（“用户”）
公共字符串getUser（）{
返回“myUser”；
}
}

但是，当我使用两个JAR部署EAR时，会出现以下异常：

SEVERE: Exception while loading the app : WELD-001408 Unsatisfied dependencies for type [String] with qualifiers [@Named] at injection point [[parameter 1] of [constructor] @Inject public com.example.MyManagedBean(String)]
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [String] with qualifiers [@Named] at injection point [[parameter 1] of [constructor] @Inject public com.example.MyManagedBean(String)]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:270)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:396)
    at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:190)
    at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
    at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:306)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:462)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
    at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:382)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1064)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1244)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1232)
    at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:459)
    at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:209)
    at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
    at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:238)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:828)
    at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:725)
    at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
    at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
    at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
    at java.lang.Thread.run(Thread.java:662)

有什么想法吗

---

谢谢

确保这两个JAR都是“bean档案”——即它们都有

META-INF/beans.xml

一件事，您必须创建Qulifier注释，以精确指定应该注入的内容

@Qualifier
@Retention(RUNTIME)
@Target({METHOD, FIELD, PARAMETER, TYPE})
public @interface UserConfiguration { }

然后

 @Produces
 @UserConfiguration
 @Named("user")
 public String getUser(){
  return "myUser";
 }

注射用

@Inject
public MyManagedBean(@UserConfiguration String user){
    this.user = user;
}

---

另请参见

我遇到了完全相同的问题，我能够解决它，但我使用耳朵来组合罐子

耳朵布局

project.ear
|-- META-INF 
|      |-- MANIFEST.MF
|      |-- application.xml*
|-- one.jar (bean archive)
|      |-- META-INF
|      |      |-- beans.xml
|      |-- <code>
|-- two.jar (ejb)

• application.xml

测试应用
2.jar
1.jar

这样做可以使容器中的one.jar对two.jar可用

---

-kurt

是的，两个JAR都有META-INF/beans.xml，没有限定符注释，它应该有@Default限定符。。。不是吗？我相信这是你问题的正确答案，我有完全相同的问题，如果你找到解决方案，请告诉我。

<application>
  <display-name>test-application</display-name>
  <module>
    <ejb>two.jar</ejb>
  </module>
  <module>
    <java>one.jar</java>
  </module>
</application>