如何在JBoss 6.3上部署Spring管理的JPA应用程序EAP

Question

我有一个java web应用程序。此应用程序使用JPA进行持久化。持久性由Spring管理。此应用程序可以轻松部署在Tomcat上，只需将war文件放入webapps即可。但是在JBoss中部署这个应用程序几天后对我来说成了一场噩梦。我无法在此网站上找到合适的帖子来解决此问题。

Answer 1

首先，你需要配置一个数据源（我使用的是mysql数据库）。我的JBoss安装在C:\jboss-eap-6.3\下，我用的是windows操作系统。 步骤： 1.在C:\jboss-eap-6.3\modules下创建一个目录结构com\mysql\main。您将以C:\jboss-eap-6.3\modules\com\mysql\main目录结构结束。 2.在main目录中创建一个xml文件module.xml。另外在同一个目录中放入mysql驱动程序jar mysql-connector-java-5.1.23-bin.jar。最后，您将在C:\jboss-eap-6.3\modules\com\mysql\main中有module.xml和mysql-connector-java-5.1.23-bin.jar。 3.复制以下xml内容module.xml

<?xml version="1.0" encoding="UTF-8"?> 
<module xmlns="urn:jboss:module:1.0" name="com.mysql"> 
    <resources> 
     <resource-root path="mysql-connector-java-5.1.23-bin.jar"/> 
    </resources> 
    <dependencies> 
     <module name="javax.api"/> 
     <module name="javax.transaction.api"/> 
    </dependencies> 
</module> 

4.找到C:\jboss-eap-6.3\standalone\configuration目录中的文件standalone.xml。用你最喜欢的文本编辑器打开这个文件。找到datasource子系统，即此行<subsystem xmlns="urn:jboss:domain:datasources:1.2">。在drivers元素下添加xml片段。

<driver name="mysqlDriver" module="com.mysql"> 
    <xa-datasource-class>com.mysql.jdbc.Driver</xa-datasource-class> 
</driver> 

添加下面的xml片段下datasources元素：

<datasource jndi-name="java:jboss/datasources/MYSQLDATASOURCE" pool-name="MYSQLDATASOURCE" enabled="true" use-java-context="true"> 
    <connection-url>jdbc:mysql://localhost:3306/databaseName</connection-url> 
    <driver>mysqlDriver</driver> 
    <security> 
    <user-name>root</user-name> 
    <password>databasepassword</password> 
    </security> 
</datasource> 

在这一点上，你与datasource配置完成。

接下来是配置您的persistence.xml和applicationContext.xml。 的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="erPU"> 
     <class>..</class> <!--Contains all your Entity classes--> 
     <properties>    
      <property name="hibernate.show_sql" value="false" /> 
      <property name="hibernate.format_sql" value="false" /> 
      <property name="jboss.as.jpa.providerModule" value="application" /> 
      <property name="jboss.as.jpa.managed" value="false" /> 
      <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>   
     </properties> 
    </persistence-unit>  
</persistence> 

<!--jboss.as.jpa.providerModule  is the name of the persistence provider module (default is org.hibernate). Should be hibernate3-bundled if Hibernate 3 jars are in the application archive (adapterModule and adapterClass will automatically be set for hibernate3-bundled). Should be application, if a persistence provider is packaged with the application. --> 
<!--jboss.as.jpa.managed can be set to false to disable container managed JPA access to the persistence unit. The default is true, which enables container managed JPA access to the persistence unit. This is typically set to false for Seam 2.x + Spring applications. --> 

的applicationContext.xml

<?xml version="1.0" encoding="UTF-8"?> 
<beans xmlns="http://www.springframework.org/schema/beans" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
     xmlns:context="http://www.springframework.org/schema/context" 
     xmlns:jee="http://www.springframework.org/schema/jee" 
     xmlns:tx="http://www.springframework.org/schema/tx"  

     xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd 
      http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd 
      http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-3.0.xsd 
      http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd 
"> 

    <context:annotation-config /> 
    <context:component-scan base-package="..." /><!--Package base name to scan for annotations -->   

    <jee:jndi-lookup id="dataSource" jndi-name="java:jboss/datasources/MYSQLDATASOURCE" expected-type="javax.sql.DataSource"/>  
    <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> 
     <property name="dataSource" ref="dataSource" /> 
     <property name="packagesToScan" value="..." /><!--Packages to scan for entities--> 
     <property name="persistenceUnitName" value="erPU" /> 
     <property name="persistenceXmlLocation" value="classpath*:META-INF/persistence.xml"/> 
     <property name="jpaVendorAdapter"> 
      <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"> 
       <property name="showSql" value="false" /> 
      </bean> 
     </property> 
     <property name="jpaPropertyMap"> 
      <map> 
       <entry key="hibernate.hbm2ddl.auto" value="update" /> 
       <entry key="hibernate.format_sql" value="false" /> 
       <entry key="hibernate.show_sql" value="false" /> 
       <entry key="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" /> 
      </map> 
     </property> 
    </bean>  
    <bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/> 
    <bean class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor"/> 
    <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager"> 
     <property name="entityManagerFactory" ref="entityManagerFactory" /> 
    </bean> 
    <tx:annotation-driven transaction-manager="transactionManager"/> 
</beans> 

注：无论persistence.xml的位置，你需要告诉春天在persistence.xml所在。该literature below was extracted from

Using Spring-managed persistence units 

Spring applications running in JBoss AS7 may also create persistence units on their own, using the LocalContainerEntityManagerFactoryBean. This is what these applications need to consider: 
Placement of the persistence unit definitions 

When the application server encounters a deployment that has a file named META-INF/persistence.xml (or, for that matter, WEB-INF/classes/META-INF/persistence.xml), it will attempt to create a persistence unit based on what is provided in the file. In most cases, such definition files are not compliant with the Java EE requirements, mostly because required elements such as the datasource of the persistence unit are supposed to be provided by the Spring context definitions, which will fail the deployment of the persistence unit, and consequently of the entire deployment. 

Spring applications can easily avoid this type of conflict, by using a feature of the LocalContainerEntityManagerFactoryBean which is designed for this purpose. Persistence unit definition files can exist in other locations than META-INF/persistence.xml and the location can be indicated through the persistenceXmlLocation property of the factory bean class. 

Assuming that the persistence unit is in the META-INF/jpa-persistence.xml, the corresponding definition can be: 
<bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> 
     <property name="persistenceXmlLocation" value="classpath*:META-INF/jpa-persistence.xml"/> 
     <!-- other definitions --> 
</bean> 

WEB-INF/jboss的部署，structure.xml 最后，您需要WEB-INF下创建jboss-deployment-structure.xml。该文件的内容应该是：

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0"> 
    <deployment> 
    <exclusions> 
     <module name="org.hibernate"/> 
    </exclusions> 
    </deployment> 
</jboss-deployment-structure> 

这样做的原因是：

Since the LocalContainerEntityManagerFactoryBean and the corresponding HibernateJpaVendorAdapter are based on Hibernate 3, it is required to use that version with the application. Therefore, the Hibernate 3 jars must be included in the deployment. At the same time, due the presence of @PersistenceUnit or @PersistenceContext annotations on the application classes, the application server will automatically add the 'org.hibernate' module as a dependency. 

This can be avoided by instructing the server to exclude the module from the deployment's list of dependencies. 

最后，您的应用程序捆绑在一起的JPA库必须版本3.x