I refer to your first post. In fact, I see some flaws right there already.
 In the two @ComponentScan annotations (one in an expanded form with basePacages, one in a concised form without, which is fine though), they refer to basePackages either "spitter" and "spitter.web". In fact, there isn't any package of that sort, it should be "spittr" and "spittr.web" respectively. I then check out the book referred, I conclude that the book has made these annoying typos - at a terrible key data to make such kind of typos. They should be read as I mentioned. (Two places to correct.)
 Then the "spittr.web" appears in the WebConfig class which has the purpose of sending you a resolver for a view. But your controller HomeController is pretended to be located in the package spittr.config, meaning incorrect and the @ComponentScan will never find it. Hence, your HomeController should be placed in the package spittr.web instead of spittr.config.
[2.1] In case you seem to have only the directory structure spittr/config. You should made the new directory spittr/web and place the HomeController.java there instead of the placing now in spittr/config.
 After build and deploy, you should access to http://localhost:8080/spittr/ with a slash only at the end as specified in the original @RequestMapping value also with a spittr in lower-case "s".