如何解决移除RESTful服务后运行项目时的Hibernate报错？

Hey there, let’s work through this Hibernate issue you’re hitting on WildFly after adding and removing RESTful Web Services. Here are targeted steps to diagnose and fix the problem:

1. 清理残留依赖与部署文件 #

Adding and removing REST services often leaves behind conflicting dependencies or stale deployment artifacts:

• Open your project's dependency config file (pom.xml for Maven, build.gradle for Gradle) and double-check for duplicate or leftover Hibernate/JAX-RS related dependencies. Make sure only the necessary versions are included, matching what WildFly EAP 7.1 supports.
• Navigate to C:\Users\HP\Desktop\Stage 2018\jboss-eap-7.1\standalone\deployments and delete all files related to px-fs-web-stage (including .deployed, .failed, or .pending marker files). This ensures a fresh deployment without leftover cruft.

2. Validate Hibernate Configuration Files #

It’s easy to accidentally tweak Hibernate configs when modifying REST services. Check these files carefully:

• Open hibernate.cfg.xml or persistence.xml and verify that entity scan paths are correct (no missing or incorrect package names).
• Confirm database connection details (URL, username, password) haven’t been altered.
• Look for duplicate entity mappings—sometimes REST setup can add unintended entries here.

3. Check WildFly Server Configuration #

WildFly’s built-in JAX-RS and Hibernate modules can clash if REST-related changes left residual configs:

• Open C:\Users\HP\Desktop\Stage 2018\jboss-eap-7.1\standalone\configuration\standalone.xml and inspect the subsystem section. Ensure the jaxrs and hibernate-orm subsystems are configured correctly, with no extra or invalid entries added during your REST service work.
• If you added custom modules for REST services earlier, remove them from WildFly’s modules directory to prevent interference with Hibernate’s class loading.

4. Grab the Full Error Log #

The deployment snippet you shared doesn’t include the actual error stack trace, which is critical for pinpointing the issue:

• Go to C:\Users\HP\Desktop\Stage 2018\jboss-eap-7.1\standalone\log and open server.log. Search for ERROR entries around the time of your deployment—look for messages related to class not found, Hibernate mapping failures, or dependency conflicts. Sharing this specific log will let us zero in on the root cause faster.

5. Rebuild the Project from Scratch #

Stale build caches are a common culprit after modifying project structure:

• Run mvn clean install (Maven) or ./gradlew clean build (Gradle) to wipe old build artifacts and rebuild your project.
• Clear your IDE’s cache too—for IntelliJ use File > Invalidate Caches..., for Eclipse use Project > Clean...—to ensure old configs aren’t being reused.

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