-
1. Re: Regression behaviour problem between JBoss 4/Tomcat and Wildfly 10/Undertow
jaikiran Sep 12, 2017 10:25 AM (in response to gir489)I think you can control that by setting a response code of your choice as noted in the undertow subsystem's schema wildfly/wildfly-undertow_3_1.xsd at master · wildfly/wildfly · GitHub . The default is 404. Of course, this won't mean that the server will wait for the web application to be deployed before responding.
-
2. Re: Regression behaviour problem between JBoss 4/Tomcat and Wildfly 10/Undertow
gir489 Sep 12, 2017 10:40 AM (in response to jaikiran)Yeah that's not what we want. Ideal scenario is for the server to wait until all services are deployed to continue forwarding the request.
-
3. Re: Regression behaviour problem between JBoss 4/Tomcat and Wildfly 10/Undertow
gir489 Sep 12, 2017 12:53 PM (in response to gir489)We have decided to use Undertow's default error page to forward the user to a shim page, that just checks if Struts is deployed, then reloads the center page with the actual Struts action. We found this to be a much better solution, than abusing a quirk in a legacy system. Once the server is loaded, we then use web.xml's 404 page to handle real 404 errors the user encounters.
-
4. Re: Regression behaviour problem between JBoss 4/Tomcat and Wildfly 10/Undertow
ctomc Sep 13, 2017 8:42 AM (in response to gir489)1 of 1 people found this helpfulsetting default-response-code attribute to 503 for host should do the same thing.
-
5. Re: Regression behaviour problem between JBoss 4/Tomcat and Wildfly 10/Undertow
gir489 Sep 13, 2017 9:56 AM (in response to ctomc)Thanks Tomaz. That at least answers our question of solving (at least until we write the shim page) the legacy concern of it not doing what it did before. We have to have a design meeting about what the page is going to look like, what it's going to do, etc etc before we can even develop the shim page. Right now it's just a simple HTML page that spits out ¯\_(ツ)_/¯ because I didn't know what to put in there.