Not so long time ago I wrote a post about HTTP sessions in a Spring MVC application. That was the simple article with an emphasis on practical aspect of usage. In the end of the post I promised to write more advanced topic dedicated to the sessions in Spring MVC applications. So I'm going to publish this stuff.
Monthly Archives June 2013
Drop-down lists are the one of the most frequent elements in web forms. In HTML you can create such control using appropriate tags: < form:select > - parent tag of drop-down list and < form:option > - child tag of < form:select > tag. Spring MVC tag library has its own solution for the drop-down lists. In this post I will write about < form:select >, < form:option >, and < form:options > tags.
This time I want to talk about Strategy design pattern. In this way I start articles about behavioral design patterns. These kind of patterns represent some schemas of interaction between objects to make a code more flexible and well organized.The most essential point of this approach is loose coupling between objects.
It's hard to imagine a web-application which doesn't has some validation logic for an user data. Almost all user's data has some constraints, e.g. date of birth should consist of day, month, year etc. Spring MVC has its own solution for the data validation, and it's become available with the help of Validator interface.
The one of the most simplest things which you can implement in your application is MessageSource. Of course it make sense only after you have set up basic settings for a Spring MVC application. So in this tutorial I will demonstrate an example of MessageSource usage. As usually I'm going to use a java-based configuration.