Spring Boot 3.x兼容Apache Olingo V4：javax转Jakarta方案及升级咨询

一、Olingo Jakarta适配版本现状 #

Apache Olingo 4.9.0及之前版本仅支持javax API，官方暂未发布适配Jakarta EE的稳定版本。不过Olingo 5.x版本的开发路线已包含Jakarta EE迁移计划，目前处于开发阶段，尚未推出正式版。

二、现有兼容解决方案（无需降级Spring Boot） #

方案1：使用Jakarta迁移工具包自动转换依赖 #

借助Eclipse提供的迁移工具，将Olingo相关的javax包自动转换为jakarta对应包，步骤如下：

1. 在pom.xml中引入迁移插件依赖：

<dependency>
    <groupId>org.eclipse.transformer</groupId>
    <artifactId>transformer-maven-plugin</artifactId>
    <version>0.2.0</version>
    <executions>
        <execution>
            <phase>process-classes</phase>
            <goals>
                <goal>transform</goal>
            </goals>
            <configuration>
                <rules>org.eclipse.transformer.jakarta</rules>
                <transformPaths>
                    <transformPath>
                        <dir>${project.build.outputDirectory}</dir>
                    </transformPath>
                </transformPaths>
            </configuration>
        </execution>
    </executions>
</dependency>

2. 修改代码导入：将javax.servlet.http.HttpServletRequest/HttpServletResponse替换为jakarta.servlet.http.HttpServletRequest/HttpServletResponse
3. 构建项目后，工具会自动转换Olingo依赖中的javax类为jakarta版本，确保Spring容器能正确识别

方案2：自定义Servlet适配层 #

编写适配类，将Jakarta Servlet对象转换为Olingo所需的javax Servlet对象，无需修改Olingo依赖：

import jakarta.servlet.http.HttpServletRequest;
import jakarta.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpServletRequestWrapper;
import javax.servlet.http.HttpServletResponseWrapper;

// Jakarta请求转javax请求的适配类
public class JakartaToJavaxRequestWrapper extends HttpServletRequestWrapper {
    private final HttpServletRequest jakartaRequest;

    public JakartaToJavaxRequestWrapper(HttpServletRequest jakartaRequest) {
        super(new javax.servlet.http.HttpServletRequest() {
            @Override
            public String getMethod() {
                return jakartaRequest.getMethod();
            }
            @Override
            public String getRequestURI() {
                return jakartaRequest.getRequestURI();
            }
            // 实现javax.servlet.http.HttpServletRequest的其他方法，均委托给jakartaRequest
        });
        this.jakartaRequest = jakartaRequest;
    }
}

// Jakarta响应转javax响应的适配类
public class JakartaToJavaxResponseWrapper extends HttpServletResponseWrapper {
    private final HttpServletResponse jakartaResponse;

    public JakartaToJavaxResponseWrapper(HttpServletResponse jakartaResponse) {
        super(new javax.servlet.http.HttpServletResponse() {
            @Override
            public void setStatus(int sc) {
                jakartaResponse.setStatus(sc);
            }
            @Override
            public java.io.PrintWriter getWriter() throws java.io.IOException {
                return jakartaResponse.getWriter();
            }
            // 实现javax.servlet.http.HttpServletResponse的其他方法，均委托给jakartaResponse
        });
        this.jakartaResponse = jakartaResponse;
    }
}

修改控制器代码，使用适配类转换对象：

import jakarta.servlet.http.HttpServletRequest;
import jakarta.servlet.http.HttpServletResponse;
@RestController
@RequestMapping("odata")
public class ODataController {
    
    @Autowired
    CsdlEdmProvider edmProvider;
    
    @Autowired
    EntityCollectionProcessor collectionProcessor;

    @Autowired
    CustomServiceDocumentProcessor customServiceDocumentProcessor;

    @RequestMapping
    public void process1(HttpServletRequest request, HttpServletResponse response) {
        try {
            OData odata = OData.newInstance();
            ServiceMetadata edm = odata.createServiceMetadata(edmProvider,
                    new ArrayList<>());
            ODataHttpHandler handler = odata.createHandler(edm);
            handler.register(collectionProcessor);
            handler.register(customServiceDocumentProcessor);
            request.setAttribute("requestMapping", "/odata");
            // 用适配类转换后传入Olingo处理器
            handler.process(new JakartaToJavaxRequestWrapper(request), 
                            new JakartaToJavaxResponseWrapper(response));
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
}

方案3：尝试Olingo社区快照版（注意风险） #

社区已提供适配Jakarta的Olingo 5.x快照版本，可临时测试使用，但稳定性无法保障，不建议用于生产环境：

<repositories>
    <repository>
        <id>apache-snapshots</id>
        <url>https://repository.apache.org/content/repositories/snapshots/</url>
        <snapshots>
            <enabled>true</enabled>
        </snapshots>
    </repository>
</repositories>

<dependencies>
    <dependency>
        <groupId>org.apache.olingo</groupId>
        <artifactId>olingo-odata-server-core</artifactId>
        <version>5.0.0-SNAPSHOT</version>
    </dependency>
    <!-- 其他Olingo依赖统一替换为5.0.0-SNAPSHOT版本 -->
</dependencies>

三、注意事项 #

• 方案1的迁移工具可能存在少数类转换不彻底的情况，需手动验证OData核心功能
• 方案2的适配类需要实现javax Servlet接口的所有方法，适合Olingo使用范围较小的场景
• 方案3的快照版功能未经过充分测试，生产环境建议等待官方稳定版

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