[Q/A][Java SDK (Component)] Version 3.2 discards the servlet server and replaces it with a netty server. How to upgrade smoothly?

[uzong]

Pre-check

• I am sure that all the content I provide is in English.

Apache Dubbo Component

Java SDK (apache/dubbo)

Details

I upgraded from 3.0.10 to 3.2.16, but the rest server has discarded the servlet server and used the netty server (checked the source code and found that it was changed in 3.2)

My business application uses a lot of servlet APIs, such as HttpServletRequest to obtain headers, cookies, etc. Now after the upgrade, HttpServletRequest is null

It is impossible to achieve a smooth upgrade. Is there any way to switch to a servlet server, such as jetty, tomcat, to ensure that the application can continue to use the servlet API?

Code of Conduct

• I agree to follow this project's Code of Conduct

[AlbumenJ]

You can try Dubbo 3.3.

https://dubbo.apache.org/en/overview/mannual/java-sdk/reference-manual/protocol/triple-3.3/

[uzong]

3.3 is very powerful, but I just want my hundreds of services to be able to upgrade smoothly. It’s a pity, but all in all, thank you!