I think it could be useful to investiage different usage scenarios. There are multiple ways to deploy an app.
E.g. 'drag and drop' as in
STS-2502. Also via 'Run As >> Run On Server'. While similar, the fact that Drag and Drop works doesn't necessarily guarantee that different ways of calling "Run As >> Run On Server" works as well.
I.e. what I noticed is that "run on server" when clicking on the root of the sample project works as exepected, but trying to do the same for a specific 'view' file (in the sample in question that was 'home.jsp' the Run as command will deploy the app correctly, but it will not map the run as request to a correct URL on the server that actually is able to access that particular view.
That doesn't correspond, I think, to the problem the user was experiencing, but it is a problem that I have found.
I'm ok with labeling this bug a duplicate of
STS-2502, but I would suggest to include 'Run As >> Run On Server' for the 'home.jsp' file for MVC template as an alternate scenario that we expect should bring up a webpage rather than a 404 error.