That's routing to the right page, transaction and session control, storing the text of the message in a separate class than the one that returns the response, and using a template to return the resulting HTML.
Looking at the section with the actual example code in it, you could do it in about half that, if you wanted a simple version that just returned "Hello World".
If you don't want routing, templating, separation of concerns, etc. then you wouldn't be using a framework like that, of course.
I think its satirical. We all know Java's Hello World is ~10 lines long. I think the point/joke is that Java EE devs don't keep things simple.
Or rather, better put, Java EE devs always want "routing, templating, separation of concerns", because they consider it better, no matter the current problem at hand.
That's routing to the right page, transaction and session control, storing the text of the message in a separate class than the one that returns the response, and using a template to return the resulting HTML.
Looking at the section with the actual example code in it, you could do it in about half that, if you wanted a simple version that just returned "Hello World".
If you don't want routing, templating, separation of concerns, etc. then you wouldn't be using a framework like that, of course.