WEB-INF / classes中的war包中的EJB 3.1 - javax.ejb.CreateException：无法创建无状态EJB
[英]EJB 3.1 in war package in WEB-INF/classes - javax.ejb.CreateException: Could not create stateless EJB
问题描述
I think, I misunderstood rules of packaging ejb beans in war package. 
我想，我误解了在战争包中包装ejb bean的规则。
Goal: I want to use ejb beans in war package. 目标：我想在war包中使用ejb bean。
Scenario: I have some bean in my war: 场景：我的战争中有一些豆子：
@Stateless
public class RegistrationServiceBean {
@PersistenceContext(unitName = "Utopia")
EntityManager em;
public RegistrationServiceBean() {}
@Schedule(hour = "*", minute = "*", second = "*/15")
public void baseRegistration() {
System.out.println("call from ejb!!");
}
public void saveTempPartner(OasysPartnerTempEntity part) {
em.persist(part);
em.flush();
}
}
It successfully deploying to glassfish server (ogs 3.0.1) : 它成功部署到glassfish服务器（ogs 3.0.1）：
[#|2010-07-02T16:53:59.728+0300|INFO|oracle-glassfish3.0.1|javax.enterprise.system.container.ejb.com.sun.ejb.containers|_ThreadID=36;_ThreadName=Thread-1;|Portable JNDI names for EJB RegistrationServiceBean : [java:global/oasys/hydra/RegistrationServiceBean!ua.co.oasys.hydra.beans.RegistrationServiceBean, java:global/oasys/hydra/RegistrationServiceBean]|#]
But when the scheduler is starting I get : 但是当调度程序启动时，我得到：
[#|2010-07-02T16:54:20.004+0300|WARNING|oracle-glassfish3.0.1|javax.enterprise.system.container.ejb.com.sun.ejb.containers|_ThreadID=38;_ThreadName=Thread-1;|A system exception occurred during an invocation on EJB RegistrationServiceBean method public void ua.co.oasys.hydra.beans.RegistrationServiceBean.baseRegistration() javax.ejb.EJBException: javax.ejb.EJBException: javax.ejb.CreateException: Could not create stateless EJB at com.sun.ejb.containers.StatelessSessionContainer._getContext(StatelessSessionContainer.java:448) at com.sun.ejb.containers.BaseContainer.getContext(BaseContainer.java:2467) at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1860) at com.sun.ejb.containers.BaseContainer.callEJBTimeout(BaseContainer.java:3962) at com.sun.ejb.containers.EJBTimerService.deliverTimeout(EJBTimerService.java:1667) at com.sun.ejb.containers.EJBTimerService.access$100(EJBTimerService.java:98) at com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.run(EJBTimerService
All application packaged in in ear with war inside, it works good if I am deploying ejb in ejb-jar, but is not what I want. 所有的应用程序都包含在内部的war中，如果我在ejb-jar中部署ejb，它的效果很好，但不是我想要的。
After I removed weld dependency, I got exception during deployment: 删除焊接依赖项后，我在部署期间遇到异常：
com.sun.enterprise.admin.cli.CommandException: remote failure: Exception while loading the app : org.glassfish.deployment.common.DeploymentException: by java.lang.NoClassDefFoundError: ua/co/oasys/hydra/beans/RegistrationServiceBean
It is similar to glassfish bug , but I am not sure . 它类似于玻璃鱼 ，但我不确定。
updates: web.xml: 更新：web.xml：
<?xml version="1.0" encoding="UTF-8"?> <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<display-name>CO UA Partners</display-name>
<description>CO UA Partners Site</description>
<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
</context-param>
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
<!--Prime Faces-->
<context-param>
<param-name>primefaces.skin</param-name>
<param-value>sam</param-value>
</context-param>
<!--Prime Faces end-->
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<context-param>
<param-name>javax.faces.FACELETS_SKIP_COMMENTS</param-name>
<param-value>true</param-value>
</context-param>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>faces/index.xhtml</welcome-file>
</welcome-file-list>
<security-role>
<role-name>manager</role-name>
</security-role>
<security-constraint>
<web-resource-collection>
<web-resource-name>Manager Pages</web-resource-name>
<url-pattern>/faces/partner/manager/*</url-pattern>
<url-pattern>/partner/manager/*</url-pattern>
<url-pattern>/partner/*</url-pattern>
<url-pattern>/faces/partner/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>manager</role-name>
</auth-constraint>
</security-constraint>
<security-role>
<role-name>admin</role-name>
</security-role>
<security-constraint>
<web-resource-collection>
<web-resource-name>Admin Pages</web-resource-name>
<url-pattern>/faces/partner/admin/*</url-pattern>
<url-pattern>/partner/admin/*</url-pattern>
<url-pattern>/partner/*</url-pattern>
<url-pattern>/faces/partner/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>admin</role-name>
</auth-constraint>
</security-constraint>
<!--roots-->
<security-role>
<role-name>rmanager</role-name>
</security-role>
<security-role>
<role-name>radmin</role-name>
</security-role>
<security-role>
<role-name>bookkeper</role-name>
</security-role>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>oasysRealm</realm-name>
<form-login-config>
<form-login-page>/faces/login.xhtml</form-login-page>
<form-error-page>/faces/loginError.xhtml</form-error-page>
</form-login-config>
</login-config>
</web-app>
NoClassDefFoundError exception : NoClassDefFoundError异常：
[#|2010-07-04T16:16:26.401+0300|SEVERE|oracle-glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=25;_ThreadName=Thread-1;|Exception while loading the app org.glassfish.deployment.common.DeploymentException: by java.lang.NoClassDefFoundError: ua/co/oasys/hydra/RegistrationServiceBea at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167) 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.CommandRu
Update 2: 更新2：
If remove/rename beans.xml file ejbs deployed successfully. 如果删除/重命名beans.xml文件ejbs已成功部署。
Update 3: 更新3：
oasys.ear oasys.ear
jar xfv ~/Sites/workspace/Intellij_IDEA_9/Oasys/Oasys-ear/target/oasys.ear created: META-INF/ inflated: META-INF/MANIFEST.MF created: lib/ inflated: fenix.jar inflated: hydra.war inflated: javax.inject-1.jar inflated: jboss-interceptor-api-1.1-CR1.jar inflated: jsr250-api-1.0.jar inflated: lib/cdi-api-1.0-CR4.jar inflated: lib/eclipselink-2.1.0-SNAPSHOT.jar inflated: lib/javax.persistence-2.0.0.jar inflated: lib/slf4j-api-1.6.0.jar inflated: lib/slf4j-jdk14-1.6.0.jar inflated: lib/utopia.jar inflated: lib/weld-logger-1.0.0-CR2.jar inflated: META-INF/application.xml
created: META-INF/maven/ created: META-INF/maven/ua.co.oasys/ created: META-INF/maven/ua.co.oasys/oasys-ear/ inflated: META-INF/maven/ua.co.oasys/oasys-ear/pom.xml inflated: META-INF/maven/ua.co.oasys/oasys-ear/pom.properties
hydra.war hydra.war
jar xfv ~/Sites/workspace/Intellij_IDEA_9/Oasys/Hydra/target/hydra.war created: META-INF/ inflated: META-INF/MANIFEST.MF created: partner/ created: partner/admin/
created: partner/manager/ created: resources/ created: resources/css/
created: resources/css/sam/ created: resources/css/sam/images/ created: resources/layout/ created: resources/security/ created: root/
created: root/admin/ created: root/bookkeeper/ created: root/manager/ created: WEB-INF/
created: WEB-INF/classes/ created: WEB-INF/classes/ua/ created: WEB-INF/classes/ua/co/ created: WEB-INF/classes/ua/co/oasys/
created: WEB-INF/classes/ua/co/oasys/hydra/
created: WEB-INF/classes/ua/co/oasys/hydra/common/ created: WEB-INF/classes/ua/co/oasys/hydra/i18n/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/registration/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/security/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/ua/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/ua/co/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/ua/co/oasys/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/ua/co/oasys/hydra/ created: WEB-INF/classes/ua/co/oasys/hydra/mb/ua/co/oasys/hydra/i18n/ created: WEB-INF/lib/ inflated: html5.html inflated: index.xhtml inflated: login.xhtml inflated: loginError.xhtml inflated: partner/admin/admin.xhtml inflated: partner/manager/manager.xhtml inflated: partner/partner.xhtml inflated: register.xhtml inflated: resources/css/cssLayout.css inflated: resources/css/default.css inflated: resources/css/master.css inflated: resources/css/sam/images/sprite.png inflated: resources/css/sam/images/ui-inflated: WEB-INF/lib/primefaces-2.1.RC1-SNAPSHOT.jar inflated: WEB-INF/sun-web.xml inflated: WEB-INF/web.xml created: META-INF/maven/ created: META-INF/maven/ua.co.oasys/ created: META-INF/maven/ua.co.oasys/hydra/ inflated: META-INF/maven/ua.co.oasys/hydra/pom.xml inflated: META-INF/maven/ua.co.oasys/hydra/pom.properties
- Q1: is it passable to use ejb beans packaged in war (specification sad that is true)? Q1：使用战争中包装的ejb bean是否合格（规范令人遗憾）？
- Q2: should I describe some configuration by ejb-jar.xml ? Q2：我应该通过ejb-jar.xml描述一些配置吗？
- Q3: what could be a cause of a problem? 问题3：可能导致问题的原因是什么？
3 个解决方案
解决方案1
1 2010-07-02 20:04:00
It is similar to glassfish bug, but I am not sure .
Hard to say, especially since you didn't provide the stacktrace for the NoClassDefFoundError , but the scenario seems different anyway. 很难说，特别是因为你没有为NoClassDefFoundError提供堆栈NoClassDefFoundError ，但无论如何情况似乎都不同。
Q1: is it passable to use ejb beans packaged in war (specification sad that is true)?
Definitely. 当然。 You can either put EJB classes in WEB-INF/classes or package them as EJB-JAR and put them in WEB-INF/lib . 您可以将EJB类放在WEB-INF/classes也可以将它们打包为EJB-JAR并将它们放在WEB-INF/lib 。 I have several demo applications doing this. 我有几个演示应用程序这样做。
Q2: should I describe some configuration by ejb-jar.xml ?
No, nothing forces you to do so. 不，没有什么能迫使你这样做。
Q3: what could be a cause of a problem?
The problem is that I couldn't reproduce the problem... I've deployed your EJB in a webapp with [ejb, jpa, web, webservices, weld] engines enabled (I just modified it to insert an Entity of mine in the scheduled method) and it just works. 问题是我无法重现这个问题......我已经在启用了[ejb, jpa, web, webservices, weld]引擎的webapp中部署了你的EJB（我只是修改它以插入我的实体）预定的方法），它只是工作。 Tested with an up-to-date version of GlassFish 3.0.1. 使用最新版本的GlassFish 3.0.1进行测试。 So I suspect a mistake or configuration problem on your side. 所以我怀疑你身边有错误或配置问题。
Just in case, can you provide the output of jar xfv yourapp.war (and also show your web.xml )? 为了以防万一，你能提供jar xfv yourapp.war的输出（并显示你的web.xml ）吗？
解决方案2
1 已采纳 2010-07-04 19:24:12
See: CDI with ejb 3.1 , weld-logger on glassfish v3.0.1 There I Describe step to reproduce this issues. 请参阅： 带有ejb 3.1的CDI，glassfish v3.0.1上的焊接记录器我在此描述重现此问题的步骤。
As I understand - there is no possibility to use CDI & EJB in one web module packaged in ear archive together and deployed t glassfish 3.0.1. 据我了解 - 不可能在一个包含在ear存档中的Web模块中使用CDI和EJB并部署t glassfish 3.0.1。
Current design is to separate ejb and war module - at least it works for me. 目前的设计是将ejb和war模块分开 - 至少它对我有用。
解决方案3
0 2010-07-02 20:00:24
EJBs packaged in a WAR are using the web / lite profile of EE6. 打包在WAR中的EJB使用EE6的web / lite配置文件。 As far as I know, timers and some other features are not supported in this profile. 据我所知，此配置文件不支持计时器和其他一些功能。 So if you want to use timers you would have to package your ejbs in the traditional ejbjar + war + ear way. 因此，如果你想使用计时器，你必须用传统的ejbjar + war + ear方式打包你的ejbs。
I could not find a reference for the web profile, this is the closest to a comparison: http://www.theserverside.com/news/1321142/Part-Three-New-Features-in-EJB-31 我找不到网络资料的参考资料，这是最接近的比较： http ： //www.theserverside.com/news/1321142/Part-Three-New-Features-in-EJB-31
Edit: I stand corrected, war packaging is actually described in jsr 318, EJB 3.1. 编辑：我认为，战争包装实际上是在jsr 318，EJB 3.1中描述的。 Since I could not find any restrictions on available features in that section of the spec, timers should also work in an ejb packaged in a war. 由于我在规范的该部分中找不到对可用功能的任何限制，因此计时器也应该在战争中打包的ejb中工作。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.