Hi everyone, I was working on a local fix for TRUNK-6590 and want to verify my testing method. I spun up the openmrs-core repository using both the baseline (-f docker-compose.yml) and override (docker-compose.override.yml) configurations.
The database and backend booted perfectly.
Hitting the base /openmrs/ path returns a 404 (the bug).
However, hitting http://localhost:8080/openmrs/index.htm directly also returns a 404 for me, even though the ticket mentions this page displays properly.
Am I missing something in my configuration, or is this expected (i.e., because the core Docker setup doesn’t bundle the Legacy UI module)? If this is expected, what is the recommended way to verify this routing fix locally before opening a PR (e.g., checking for a 302 redirect via curl)?
Thanks, I don’t get the same error with Jetty. When running mvn jetty:run from the webapp folder, the application boots correctly and returns a 302 Found redirecting to /initialsetup for both /openmrs/ and /openmrs/index.htm.
However, the Docker environment (which uses Tomcat 11) was consistently returning a 404. After digging into the logs, I found that the DispatcherServlet was intercepting the welcome-file request but failing because there was no explicit mapping for the root path or the welcome file in the Spring context.
I have implemented a fix by:
Adding a / mapping for the openmrs servlet in web.xml.
Adding a mvc:view-controller redirect in openmrs-servlet.xml to explicitly route the root path to index.htm.
