Java EE 6 + JPA - 異常：消息驅動Bean不能被管理的bean

Question

我創建了一個Enterprise ApplicationCustomerApp，它也生成了兩個項目CustomerApp-ejb和CustomerApp-war。在CustomerApp-ejb中，我創建瞭如下的SessionBean調用CustomerSessionBean.java。

package com.customerapp.ejb; 

import javax.ejb.Stateless; 
import javax.ejb.LocalBean; 
import javax.persistence.EntityManager; 
import javax.persistence.PersistenceContext; 

@Stateless 
@LocalBean 
public class CustomerSessionBean { 
    @PersistenceContext(unitName = "CustomerApp-ejbPU") 
    private EntityManager em; 

    public void persist(Object object) { 
     em.persist(object); 
    } 
} 

現在我可以部署CustomerApp-war就好了。但是一旦我創建了消息驅動Bean，我就不能部署CustomerApp-war了。當我創建NotificationBean.java（消息驅動bean）時，在project destination選項中，我單擊添加，並有NotificationQueue爲Destination Name和Destination Type爲隊列。以下是密碼

package com.customerapp.mdb; 

import javax.ejb.ActivationConfigProperty; 
import javax.ejb.MessageDriven; 
import javax.jms.Message; 
import javax.jms.MessageListener; 

@MessageDriven(mappedName = "jms/NotificationQueue", activationConfig = { 
    @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"), 
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") 
}) 
public class NotificationBean implements MessageListener { 

    public NotificationBean() { 
    } 

    public void onMessage(Message message) { 
    } 

} 

服務器日誌說Message Driven Bean cant be managed bean。那麼我不是說它是管理bean。我在代碼中沒有@ManagedBean？

編輯：這裏是服務器日誌

[#|2010-06-03T10:02:08.172-0400|SEVERE|glassfishv3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=24;_ThreadName=Thread-1;|Exception while loading the app org.glassfish.deployment.common.DeploymentException: Message Driven Beans can't be Managed Beans 
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:169) 
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125) 
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224) 
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) 
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) 
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) 
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) 
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365) 
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204) 
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) 
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) 
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) 
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) 
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) 
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) 
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) 
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) 
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) 
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) 
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) 
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) 
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) 
at com.sun.grizzly.ContextTask.run(ContextTask.java:69) 
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) 
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) 
at java.lang.Thread.run(Thread.java:637) 
Caused by: org.jboss.weld.DefinitionException: Message Driven Beans can't be Managed Beans 
at org.jboss.weld.bean.SessionBean.checkEJBTypeAllowed(SessionBean.java:313) 
at org.jboss.weld.bean.SessionBean.initialize(SessionBean.java:122) 
at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:111) 
at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:151) 
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:367) 
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167) 
... 30 more 

Answer 1

唯一的例外是DeploymentException: Message Driven Beans can't be Managed Beans

這是a bug in GlassFish 3.0被固定在3.0.1。

• 解決辦法：刪除beans.xml（但是這將禁用CDI）
• 真正的解決方案：下載的GlassFish 3.0.1 a promoted build（問題被報告爲固定版本3.0.1-B9所以任何上級版本應工作）

低於初始答案：

---

• MDB位於何處？你有沒有把它放在CustomerApp-ejb？
• 你是什麼意思現在我可以部署CustomerApp-war就好了？您應該部署企業應用程序（CustomerApp）。
• 當部署失敗時，您在GlassFish日誌中看到了什麼？