Even if the goal was not with first implementations of REST DSL to expose
the OPTIONS verb within the DSL, I think that it makes sense to propose it (
https://issues.apache.org/jira/browse/CAMEL-9129) for the following reasons
- The browser will issue OPTIONS requests when CORS is enabled. This is
typically what will happen when the Swagger UI runs into a different HTTP
Server (8080) instead of the server running the Camel REST Endpoints
- It could also be use to reply to applications interested to know which
operations are supported by the endpoints (
We have nevertheless to review the code about the jetty, netty, netty4, ...
components to be sure that they will send a correct response when an
OPTIONS operation is issued as this is not the case for the moment.