You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuration that is applied by a context xml file can be generated into a quickstart-web.xml file. When the webapp is quickstarted, we apply both the context xml file AND the quickstart-web.xml file, which could lead to the same element being created/configured twice. I've tested this with a servlet that was defined in a context xml file: it was also generated into quickstart-web.xml file. Luckily, the StandardDescriptorProcessor that reads the quickstart-web.xml file has some protection in there for creating duplicate servlets, but it will reapply the configuration. I'm not sure of the situation with filters.
In any case, the solution would be to check the origin of the servlets/filters etc when generating the quickstart-web.xml file: any that were of programmatic/xml origin can be skipped, as they will be re-applied when the webapp is quickstarted.
The text was updated successfully, but these errors were encountered:
Jetty 10
Configuration that is applied by a context xml file can be generated into a quickstart-web.xml file. When the webapp is quickstarted, we apply both the context xml file AND the quickstart-web.xml file, which could lead to the same element being created/configured twice. I've tested this with a servlet that was defined in a context xml file: it was also generated into quickstart-web.xml file. Luckily, the StandardDescriptorProcessor that reads the quickstart-web.xml file has some protection in there for creating duplicate servlets, but it will reapply the configuration. I'm not sure of the situation with filters.
In any case, the solution would be to check the origin of the servlets/filters etc when generating the quickstart-web.xml file: any that were of programmatic/xml origin can be skipped, as they will be re-applied when the webapp is quickstarted.
The text was updated successfully, but these errors were encountered: