WebFilter开发求助：Java8+Wildfly10环境下Maven缺失依赖排查

Hey there! Let's dig into this dependency mystery—since your REST modules are running smoothly, we can focus on narrowing down what's missing or misconfigured in the problematic module. Here are practical steps to diagnose:

• Start with the error details (critical!)
  Don’t overlook the exact error messages—whether it’s a ClassNotFoundException during deployment (check Wildfly’s server.log) or a compile-time missing class from Maven. The missing class name will point you directly to the required dependency. For example, if you’re seeing errors related to javax.persistence.EntityManager, confirm if Wildfly 10’s built-in JPA module is accessible, or if you need to adjust your pom.xml.

• Verify Wildfly 10’s built-in APIs
  Wildfly 10 ships with Java EE 7 APIs. Cross-check the classes your problematic module uses against Java EE 7 specs. If you’re using classes outside this scope (e.g., newer Java EE 8 features, or third-party libraries not included in Wildfly), you’ll need to add those dependencies to your pom.xml (make sure to set the correct scope—compile if Wildfly doesn’t provide it, provided only if Wildfly includes it).

• Compare pom.xml with working REST modules
  Since your REST modules work, do a side-by-side comparison of their pom.xml files with the problematic module’s. Look for:

  • Missing provided scope dependencies that the REST module includes (e.g., javax.ws.rs-api might be in the REST pom but missing here)
  • Extra dependencies in the problematic module that could cause conflicts
  • Differences in the maven-compiler-plugin configuration (ensure source/target are set to 1.8, with Java 8 marked as provided correctly)

• Analyze your Maven dependency tree
  Run these commands in your module’s directory to uncover issues:

  • mvn dependency:tree: This will show all transitive dependencies. Look for missing artifacts, conflicting versions, or dependencies with incorrect scopes.
  • mvn dependency:analyze: Maven will flag unused dependencies and highlight classes that require dependencies you haven’t declared explicitly.

• Check Wildfly’s module directory
  Navigate to your Wildfly installation’s modules/system/layers/base folder. This contains all the modules Wildfly provides out of the box. If your code uses a package that doesn’t have a corresponding module here (e.g., a third-party library like com.google.gson), you’ll need to add it as a compile scope dependency in Maven.

• Review deployment descriptors
  If your project uses a jboss-deployment-structure.xml file, check if it’s excluding any necessary Wildfly modules or failing to import required ones. For example, if you’ve excluded the JPA module but your code uses JPA annotations, that would cause missing class errors.

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