RAP could use the updated Whiteboard Specification for registering servlets and resources:
https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.servlet.html
Currently, the RWTServlet is registered via HttpService which is contained within RAP as an updated Jakarta-compatible version:
https://github.com/eclipse-rap/org.eclipse.rap/blob/main/bundles/org.eclipse.rap.http.servlet/src/org/eclipse/rap/service/http/HttpService.java
In the best case most of the org.eclipse.rap.http.* classes can be removed if the updated Whiteboard Specification is used to register servlets/resources.
For example, Felix HTTP provides an implementation for both, the "old" HttpService and the new Whiteboard Specification:
https://github.com/apache/felix-dev/tree/master/http
RAP could use the updated Whiteboard Specification for registering servlets and resources:
https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.servlet.html
Currently, the RWTServlet is registered via
HttpServicewhich is contained within RAP as an updated Jakarta-compatible version:https://github.com/eclipse-rap/org.eclipse.rap/blob/main/bundles/org.eclipse.rap.http.servlet/src/org/eclipse/rap/service/http/HttpService.java
In the best case most of the
org.eclipse.rap.http.*classes can be removed if the updated Whiteboard Specification is used to register servlets/resources.For example, Felix HTTP provides an implementation for both, the "old" HttpService and the new Whiteboard Specification:
https://github.com/apache/felix-dev/tree/master/http