Enable web.xml to be used to configure CamelHttpTransportServlet for the servlet extension #5835
Comments
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Mar 5, 2024
…the servlet extension Fixes apache#5835
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Mar 5, 2024
…the servlet extension Fixes apache#5835
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Mar 5, 2024
…the servlet extension Fixes apache#5835
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Mar 5, 2024
…the servlet extension Fixes apache#5835
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Mar 5, 2024
…the servlet extension Fixes apache#5835
jamesnetherton
added a commit
that referenced
this issue
Mar 5, 2024
…the servlet extension Fixes #5835
jamesnetherton
added a commit
to jboss-fuse/camel-quarkus
that referenced
this issue
Mar 6, 2024
…the servlet extension Fixes apache#5835
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature here
We should consider allowing old skool
web.xmlconfiguration, as some folks may have existing apps that configure camel-servlet in this way.It's currently not possible because there is some build time validation logic that forces usage of
quarkus.camel.servlet.*properties.The text was updated successfully, but these errors were encountered: