Recently I was tasked with adding data security to an existing application. The security rules were complex, users within the same user role were supposed to be able to view and edit data differently. I decided to implement this task with a permissions based system whereby users were grouped into roles and each role had a certain set of permissions. Here's how I implemented the solution using Spring and Hibernate...

Previously, I wrote an article on how to achieve dynamic list binding in Spring MVC. Since I wrote that article, I have received emails and comments that ask (in a roundabout way) Why would I need to do this? When I wrote the other article I didn't explain the why; I just wrote the how. Here's why you need dynamic binding and the problems it is trying to solve.

How can I easily dump http POST parameters using JSTL? It is super easy...

I'm not trying to compete with Hani on this, but can we stop the absurdity and futility of debating web frameworks please? I mean does a framework really need to do anything other than help deal with a web request?

I attempted to deploy my newly created webapp onto a machine that had no access to the public internet. When the app attempted to start up, I was greeted with a nice friendly error that occurred when the xml parser attempted to validate dtd in one of my configuration files...

The Spring MVC documentation just isn't quite there. It is pretty basic, and doesn't really help with some common medium difficulty scenarios. The one I am documenting today is how to take a typical model (with lists of dependent objects), show it in a form, and get the graph back upon submission...