By mxc4
via jumpingbean.co.za
Submitted: Nov 16 2009 / 01:20
Using Wicket with Tomct form-based authentication is not ideal but in some cases, such as application migration, you are forced to make use of it for legacy reasons. This blog post explains how this was achieved on a project to enable legacy Struts code to share authentication and authorisation credentials with Wicket and not have to rewrite some legacy code.
-
Google to strip Chrome of SSL revocation checking
-
Apple pulls cloned games from App Store
-
video/presentation - Evading Pirates and Stopping Vampires using Android License Verification Library, In-App Billing, and App Engine
-
Interview with Elizabeth Naramore
-
New Apache Lucene Site!
-
Two things you thought you weren’t going to get: a manufacturing date and an SoC datasheet
Add your comment
