WAR部署失败：缺失PersistenceUnit问题求助

Let’s break down the most likely causes for your "missing PersistenceUnit" error when deploying your WAR, and walk through how to fix each one:

1. Verify Your persistence.xml Location and Content #

First, double-check the basics:

• In a WAR package, persistence.xml must live in WEB-INF/classes/META-INF/—you mentioned this is your structure, but confirm there are no typos (e.g., lowercase meta-inf instead of uppercase META-INF).
• The file’s root element must be <persistence>, and it needs a properly named <persistence-unit> node that matches what your code references. For example, if your EJB uses @PersistenceContext(unitName = "shortboxPU"), your persistence.xml should have:

  <?xml version="1.0" encoding="UTF-8"?>
  <persistence version="2.1" 
               xmlns="http://xmlns.jcp.org/xml/ns/persistence" 
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
               xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
      <persistence-unit name="shortboxPU" transaction-type="JTA">
          <!-- Match this exactly to your jboss-ds.xml JNDI name -->
          <jta-data-source>java:/jdbc/shortbox</jta-data-source>
          <!-- List your JPA entities explicitly, or set exclude-unlisted-classes to false -->
          <class>com.yourpackage.YourFirstEntity</class>
          <class>com.yourpackage.YourSecondEntity</class>
          <properties>
              <property name="hibernate.hbm2ddl.auto" value="update"/>
              <property name="hibernate.show_sql" value="true"/>
          </properties>
      </persistence-unit>
  </persistence>
  

• Ensure the transaction-type is set to JTA (required for stateless EJBs) and that <jta-data-source> perfectly matches the jndi-name in your jboss-ds.xml.

2. Validate Your jboss-ds.xml Configuration #

Your datasource needs to be fully defined and accessible to WildFly:

• Complete your jboss-ds.xml with missing details like driver references, credentials, and validation settings. A working MySQL example looks like:

  <?xml version="1.0" encoding="UTF-8"?>
  <datasources>
      <datasource jndi-name="java:/jdbc/shortbox" pool-name="mysql_pool" enabled="true" use-java-context="true">
          <connection-url>jdbc:mysql://localhost:3306/shortbox?useSSL=false&amp;serverTimezone=UTC</connection-url>
          <driver>mysql</driver>
          <security>
              <user-name>your_db_username</user-name>
              <password>your_db_password</password>
          </security>
          <validation>
              <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
              <validate-on-match>true</validate-on-match>
              <background-validation>false</background-validation>
          </validation>
      </datasource>
      <drivers>
          <driver name="mysql" module="com.mysql">
              <driver-class>com.mysql.cj.jdbc.Driver</driver-class>
          </driver>
      </drivers>
  </datasources>
  

• Confirm the MySQL driver module is installed in WildFly: Place the mysql-connector-java.jar in modules/system/layers/base/com/mysql/main/ and create a module.xml for it:

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

3. Check Code References to the Persistence Unit #

• In your stateless EJB or JAX-RS service, ensure the unitName in @PersistenceContext or @PersistenceUnit exactly matches the name attribute of <persistence-unit> in persistence.xml. A mismatch here is a super common culprit.
  Example correct usage:

  @Stateless
  public class YourEJB {
      @PersistenceContext(unitName = "shortboxPU")
      private EntityManager em;
      // ... rest of your business logic
  }
  

4. Confirm WAR Package Integrity #

• Unzip your WAR file to verify:
  • WEB-INF/classes/META-INF/ contains both persistence.xml and jboss-ds.xml (no missing files, no corrupted content).
  • Your compiled entity classes, EJBs, and JAX-RS services are present in WEB-INF/classes/.
• If you’re using Maven, ensure your src/main/resources/META-INF/ directory is configured to copy these files to the correct location in the WAR. Your pom.xml should include:

  <build>
      <resources>
          <resource>
              <directory>src/main/resources</directory>
          </resource>
      </resources>
  </build>
  

5. Dig Into WildFly’s Server Logs #

The "missing PersistenceUnit" message is often a generic top-level error. Check WildFly’s standalone/log/server.log for more specific details—you might find:

• XML parsing errors in persistence.xml or jboss-ds.xml
• A "datasource not found" error for java:/jdbc/shortbox
• Issues scanning your JPA entity classes

These details will point you directly to the root cause.

内容的提问来源于stack exchange，提问作者Christian Riese