Secure the app. Now you can only login. It's not so good, that we must
define the Applicationcontext twice.
Now the formatter can be partial disabled with //J- and //J+
Have an running example.
Now the view are with a little bit dynamic, depending on the roles.
Created new nurl-pattern url with named parameters.
Cleanup the code and add some further documentation and test.
Put the paramter definition closer to the usage.
Using purl or nurl. url only for backward compatibility.
For post-forms I switch to named urls.
Update Spring-Security Reference RC2 -> RELEASE
URL-Building now with parameter-name.
Introduce the possibibilty to work with named parameters.
Improve thymeleaf-testing with an baseclass.
Update Spring-Security-Reference
Disable CSRF-Protection. Otherwise the login doesn't work any more.
Obviously this is for security a bad decision, but I think if you really
want to protect your app, you must think more about security.
Release 0.8
Starting 0.9