Recently I had to investigate the question of stale data that may be passed over transactional borders in our application. The application is Spring based using JPA with Hibernate to access the database. The answer to the above question is not that interesting, but to give it I had to understand how this whole stuff is set up and configured. There are are quite some resources which address something like this, but when coming to Spring, in recent time the approach to implement this when from directly using Hibernate to using Hibernate through JPA, while there are quite some books and tutorials on this, none also include specific information how to set the isolation level and what happens when you use the optimistic locking approach.
Artikel-Schlagworte: „spring 3.0“
A further detail we might want to focus on is internationalization of our form. Spring MVC does not provide any i18n features for its form tags, there are however several issue reports addressing this (form:options tag does not support i18n, form:select does not provide I18N capabilities, Provide comprehensive I18N support for the Spring form tag library and many more, for a detailed list search for ‘i18n form’ on https://jira.springsource.org/secure/IssueNavigator.jspa?mode=show&createNew=true). However these issues can be solved. (weiterlesen …)
In the previous three articles (Spring MVC forms with select drop down list, Generifing MVC spring select lists and Generic model for form select I have shown how to develop a generic dropdown list with Spring 3.0 MVC and web forms. With the heavy stuff off our backs we can focus on the details such as the order of the option list. (weiterlesen …)