Details
Description
Currently, we include copies of the Jetty configuration files in the CARGO Jetty container. That's not very good: we have to maintain files manually, follow new versions, we're not sure that it works with all Jetty flavours, etc.
We could, for example, replace the port numbers in the original file. For example, in some files, replace 8080 with the actual HTTP port, etc.
For this the new XmlReplacement API used in CARGO-839 can be used.
Issue Links
- depends upon
-
CARGO-839
Avoid having the cargo-specific XML files in the JBoss local containers
-
- is related to
-
CARGO-743
Alllow for default standalone option
-
-
CARGO-1099
Allow the XML/properties replacement engine to WARN when a replacement is not possible (instead of failing)
-
Looks like this will be very difficult to solve with Embedded Jetty containers, as these de facto do not ship with a conf folder that we can use as "base".