OpenJPA是否适用于Glassfish？

Question

是否有人成功使用OpenJPA与Glassfish？

我正在尝试将OpenJPA 2.1与Glassfish 3.1 Open Source一起使用.我按照说明将这两个集成在这里 - > http://weblogs.java.net/blog/ss141213/archive/2006/07/using_openjpa_a.html

我在Eclipse Indigo中有一个非常简单的EJB项目,具有以下内容:

• com.rares.test.Person - @Entity
• com.rares.test.PersonManager - 界面
• com.rares.test.PersonDao - @Stateless

但是,当我尝试部署时,我的Person @Entity上会出现ClassNotFoundException.投诉似乎是在我的PersonDao中实现的创建方法的Person parm(参见下面的所有代码).

我已经尝试了相同的项目而没有在persistence.xml中指定提供程序,并且该项目工作正常(能够将Person @Entity持久保存到MySql中的PERSON表).如果我没有指定提供者,我想我正在使用EclipseLink(如果我错了,请纠正我).这让我相信我没有正确配置OpenJPA和Glassfish.

堆栈跟踪

Caused by: java.lang.IllegalArgumentException: java.lang.ClassNotFoundException: com.rares.test.Person
    at serp.util.Strings.toClass(Strings.java:164)
    at serp.util.Strings.toClass(Strings.java:108)
    at serp.bytecode.BCClass.getType(BCClass.java:566)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:283)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:254)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:144)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransformer.java:124)
    at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(PersistenceProviderImpl.java:294)
    at org.glassfish.persistence.jpa.ServerProviderContainerContractInfo$1.transform(ServerProviderContainerContractInfo.java:98)
    at com.sun.enterprise.loader.ASURLClassLoader.findClass(ASURLClassLoader.java:742)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
    at java.lang.Class.privateGetPublicMethods(Class.java:2547)
    at java.lang.Class.getMethods(Class.java:1410)
    at com.sun.enterprise.deployment.EjbDescriptor.addAllInterfaceMethodsIn(EjbDescriptor.java:2327)
    at com.sun.enterprise.deployment.EjbDescriptor.getLocalRemoteBusinessMethodDescriptors(EjbDescriptor.java:2290)
    ... 40 more

com.rares.test.Person

@Entity
@Table (name="PERSON")
public class Person implements Serializable {
    private static final long serialVersionUID = 3707476467775531463L;

    @Id
    @GeneratedValue (strategy=GenerationType.IDENTITY)
    @Column private Long id;
    @Column private String name;

com.rares.test.PersonManager

public interface PersonManager {
    void create (com.rares.test.Person p);
}

com.rares.test.PersonDao

@Stateless
public class PersonDao implements PersonManager {
    @PersistenceContext (unitName="RarePersistUnit")
    protected EntityManager mgr;

    @Override
    public void create(com.rares.test.Person p) {
        mgr.persist(p); 
    }

}

persistence.xml中

<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
    <persistence-unit name="RarePersistUnit">
        <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
        <jta-data-source>jdbc/RaresMySql</jta-data-source>
        <class>com.rares.test.Person</class>        
        <properties>

        </properties>
    </persistence-unit>
</persistence>

Answer 1

注意:下面假设OpenJPA 2.1和Glassfish 3.1.结果可能因两者的版本而异.

引发的异常是OpenJPA在运行时无法执行字节码增强的典型情况.字节码增强可以在构建时或运行时完成.获得运行时支持的一个更好的选择是使用a javaagent但需要一些怪异的配置:

• 它要求您javaagent在Glassfish域配置文件中指定一个(通过在jvm-options元素下指定一个附加java-config元素),
• 并且还要从默认值${com.sun.aas.installRoot}/modules/glassfish.jarto include 修改类路径commons-lang-2.4.jar(我没有这么做,因为它会引起一个非常脆弱的设置).

可以在运行时使用的其他选项非常不稳定,并且选择使用Serp字节码增强器是在部署时抛出异常的原因.显然,由于使用了不正确的类加载器来定位类,部署时间增强无法找到持久化上下文中使用的类.在我的例子中,Glassfish EarClassLoader和EarLibClassLoader类加载器用于在两个单独的调用中加载类,两个调用都失败并显示以下消息(堆栈跟踪在这里是无关紧要的):

WARNING: LDR5207: ASURLClassLoader EarLibClassLoader : 
doneCalled = true
doneSnapshot = ASURLClassLoader.done() called ON EarLibClassLoader : 
urlSet = []
doneCalled = false 
 Parent -> org.glassfish.internal.api.DelegatingClassLoader@10e3c8c
 AT Sun Jul 17 13:27:54 IST 2011 
 BY :java.lang.Throwable: printStackTraceToString
    at com.sun.enterprise.util.Print.printStackTraceToString(Print.java:639)
    at com.sun.enterprise.loader.ASURLClassLoader.done(ASURLClassLoader.java:211)
    ...

...

WARNING: LDR5207: ASURLClassLoader EarClassLoader : 
doneCalled = true
doneSnapshot = ASURLClassLoader.done() called ON EarClassLoader : 
urlSet = [URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/eclipseApps/app-ear/app-jsf-0.0.1-SNAPSHOT_war/WEB-INF/classes/, URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/eclipseApps/app-ear/app-jsf-0.0.1-SNAPSHOT_war/WEB-INF/lib/commons-fileupload-1.2.1.jar, URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/eclipseApps/app-ear/app-jsf-0.0.1-SNAPSHOT_war/WEB-INF/lib/commons-io-1.4.jar, URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/eclipseApps/app-ear/app-jsf-0.0.1-SNAPSHOT_war/WEB-INF/lib/primefaces-3.0.M2.jar, URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/generated/ejb/app-ear/app-jsf-0.0.1-SNAPSHOT_war/, URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/eclipseApps/app-ear/app-ejb-0.0.1-SNAPSHOT_jar/, URLEntry : file:/C:/glassfish3/glassfish/domains/domain1/generated/ejb/app-ear/app-ejb-0.0.1-SNAPSHOT_jar]
doneCalled = false 
 Parent -> org.glassfish.internal.api.DelegatingClassLoader@1a3fe65
 AT Sun Jul 17 13:27:54 IST 2011 
 BY :java.lang.Throwable: printStackTraceToString
    at com.sun.enterprise.util.Print.printStackTraceToString(Print.java:639)
    at com.sun.enterprise.loader.ASURLClassLoader.done(ASURLClassLoader.java:211)
    ...

...

显然,由于某些未知原因,EJB的生成类区域在运行时不包含JPA实体类,导致无法在部署时找到类.失败的最可能原因是,虽然实体类虽然打包在EJB模块中,但它们本身可能没有放在生成的类目录中; 只有已注释的EJB类可能已放置在那里.

唯一合理的选择是使用构建时间增强,这是使用Maven POM中的以下配置正确完成的:

 <build>
     <plugins>
         <plugin>
             <groupId>org.apache.maven.plugins</groupId>
             <artifactId>maven-antrun-plugin</artifactId>
             <version>1.6</version>
                 <executions>
                     <execution>
                         <phase>process-classes</phase>
                         <configuration>
                             <tasks>
                                 <taskdef name="openjpac" classname="org.apache.openjpa.ant.PCEnhancerTask" classpathref="maven.compile.classpath"/>
                                 <openjpac>
                                     <classpath refid="maven.compile.classpath"/>
                                 </openjpac>
                             </tasks>
                         </configuration>
                         <goals>
                             <goal>run</goal>
                         </goals>
                     </execution>
                 </executions>
             </plugin>
         </plugins>
    </pluginManagement>
</build>

以上配置源自OpenJPA文档,该文档使用Maven增强类.请注意,我没有使用openjpa-maven-plugin,因为OpenJPA的2.2.0版本在编写本文时仅作为快照提供.

当然,上述任何一项都需要在Glassfish 3.1中安装OpenJPA 2.1,这是通过将以下JAR复制到${com.sun.aas.installRoot}/glassfish/lib(例如C:/glassfishv3/glassfish/lib)而不是在较旧的博客帖子上提供的复制建议${com.sun.aas.instanceRoot}/lib(例如) ,C:/glassfishv3/glassfish/domains/domain1/lib)

• 公地的BeanUtils-1.8.3.jar
• 公地集合-3.2.1.jar
• 公地DBCP-1.4.jar
• 公地郎2.4.jar
• 共享记录-1.0.4.jar
• commons-pool的-1.5.4.jar
• SERP-1.13.1.jar
• OpenJPA的-2.1.0.jar

显然,放置这些JAR ${com.sun.aas.instanceRoot}/lib会导致Maven Glassfish插件无法部署应用程序.

的其他JAR( geronimo-*,derby-*和org.apache.bval*)存在于所述的OpenJPA 2.1分布通过Glassfish的3.1提供作为Java EE 6 SDK中,Java DB执行或对Derby客户机的一部分,和JSR 303豆验证框架(Hibernate验证)内.