JBoss REST API无法启动疑与CDI相关，微服务打包配置咨询

Hey there, let's break down your problem step by step—you're migrating a monolith to Dockerized microservices with JBoss EAP7 (2.2.0-1.6.9) and hitting issues when adding CDI components. First, let's cover how to properly package your app to enable CDI, then go through common troubleshooting steps for those exceptions.

一、正确打包以启用CDI #

CDI in JBoss EAP7 relies on a few key requirements to activate—here's what you need to do:

1. 确保存在beans.xml文件 #

JBoss uses this file to trigger CDI scanning. Even an empty file works for Java EE 7+ (which EAP7 supports), but it must be in the right location:

• For WAR packages (your mention of --w... is likely referring to WAR packaging): Place it at src/main/webapp/WEB-INF/beans.xml
• For JAR modules: Place it at src/main/resources/META-INF/beans.xml

This is the most common gotcha—without this file, JBoss won't recognize your CDI beans at all.

2. 依赖配置要正确 #

JBoss EAP7 includes the Weld CDI implementation out of the box, so you don't need to bundle CDI API or Weld core in your app. If you're using Maven, set your CDI dependency to provided scope to avoid conflicts:

<dependency>
    <groupId>javax.enterprise</groupId>
    <artifactId>cdi-api</artifactId>
    <version>2.0</version>
    <scope>provided</scope>
</dependency>

3. 标准WAR打包 & Docker部署 #

For your WAR package, use standard build tools like Maven or Gradle—no special flags are needed beyond ensuring the above two steps are done. For example, with Maven:

mvn clean package

When building your Docker image, make sure to copy the generated WAR into JBoss's deployment directory. Your Dockerfile should include something like:

FROM jboss-eap7:2.2.0-1.6.9
COPY target/your-app.war /opt/jboss/eap/standalone/deployments/

JBoss will automatically deploy the WAR and activate CDI if the beans.xml is present.

二、排查CDI异常的常见原因 #

If you've got the packaging right but still see exceptions, here are the top things to check:

• Verify CDI annotations: Double-check that your beans use valid CDI annotations (e.g., @Named, @ApplicationScoped, @Inject). Typos like @Injectt or missing scope annotations can cause the container to not recognize beans.
• Check injected beans are CDI-managed: You can only inject objects that are managed by the CDI container. If you're trying to inject a plain class without any CDI annotations, the container won't find it—add a scope annotation like @Dependent (the default) to make it manageable.
• Dig into JBoss logs: The exception stack trace will tell you exactly what's wrong. Look for Caused by sections—common issues include:
  • UnsatisfiedDependencyException: The container can't find a bean to inject (check if the bean exists and has the right qualifiers/scopes)
  • DeploymentException: Issues with beans.xml (wrong location, invalid syntax)
  • Class loading conflicts: If you accidentally bundled CDI dependencies, this can clash with JBoss's built-in Weld.
• Docker container permissions: Ensure the jboss user in the container has read access to the deployment directory and your WAR file. Sometimes file permissions from the host can cause issues when copying into the container.
• Java version compatibility: JBoss EAP7 requires Java 8. Confirm that your Docker image is using a Java 8 JDK—older/newer versions can cause unexpected CDI runtime issues.

三、快速验证CDI配置的测试方案 #

To rule out packaging issues, create a minimal test:

1. Add a simple CDI bean:

import javax.enterprise.context.ApplicationScoped;

@ApplicationScoped
public class HelloBean {
    public String sayHello() {
        return "Hello CDI!";
    }
}

2. Inject it into your REST endpoint:

import javax.inject.Inject;
import javax.ws.rs.GET;
import javax.ws.rs.Path;

@Path("/hello")
public class HelloResource {
    @Inject
    private HelloBean helloBean;

    @GET
    public String getHello() {
        return helloBean.sayHello();
    }
}

3. Ensure WEB-INF/beans.xml exists (empty is fine)
4. Build the WAR, deploy to Docker, and test the endpoint. If this works, your packaging is correct—your original exception is likely tied to a specific bean or dependency in your app.

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