Ah, this is fine. The servlet acts as the controller part of MVC. BeerExpert is the model, and it has no knowledge of the view. Controllers orchestrate the view, so they often know all about the view. Some designs have a controller servlet per page so they can hard code things like nextpage.
It is possible to build much more generic servlet controllers. Many frameworks like
Struts have exactly one servlet that uses some field on the request to look up the model and the next view. At a very high level it does something like:
Hope you're enjoying the Head First books. Let me know if all that made sense or jumped too far ahead.