Using a default "static" controller to sketch web applications with Spring
When sketching an application, I use a "standard" controller that takes the url and returns a jsp called with the same name (index.html -> index.jsp, addstuff.html -> addstuff.jsp and so on) and an empty model.
When I go deeper into the application and start writing real controllers, I substitute each of the "standard" controllers with forms/controllers that do more stuff than returning an empty model. It is a good way to have all your urls in place before you write any java code.
Of course, instead of a "jsp" you could use whatever view technology you like.
You can download the source code of my Default Spring Controller here.
When I go deeper into the application and start writing real controllers, I substitute each of the "standard" controllers with forms/controllers that do more stuff than returning an empty model. It is a good way to have all your urls in place before you write any java code.
Of course, instead of a "jsp" you could use whatever view technology you like.
You can download the source code of my Default Spring Controller here.
Comments
Post a Comment