|
Saturday, June 13, 2009
Notes on making a simple auth app using Wicket
Follow the instructions here and add the junk to your pom. You'll need to add a Run I prefer JUnit 4 to 3.8, so I removed the generated "variable" ref from my class path and added Eclipse's built-in library for JUnit 4. To keep things consistent, I modified the pom to refer to JUnit 4.. Maybe I should have let the Eclipse build reference the Maven repo rather than Eclipse for its JUnit. Hmm. Added "variable" ref for both swarm and wasp (sheesh - why two? This is so confusing) and changed my application to extend Of course, Eclipse helped me out with the stubs of the overrides of the abstract methods, so on to filling them in. So, starting with a bare-bones app, start adding security. Hmm. Not working. OK, so start with the kitchen-sink security demo app and begin deleting unneeded code. Hard, because I don't have a project and have to rely on reconstructing one from the war. Aaargh! Give up on swarm. The guy's dead anyway, so who's maintaining it? So auth-roles is the next. Generate a project using mvn. Modify the pom to include auth-roles:<dependency> <groupId>org.apache.wicket</groupId> <artifactId>wicket-auth-roles</artifactId> <version>1.4-rc4</version> </dependency> Then use Copy gibblies from the "wicket-auth-roles-example" available on Sourceforge. (It's in maven too if you know how to get it. I don't.) It has a weird structure, not like the autogenerated one with the embedded Jelly, so that's why we have to copy/paste. A couple little syntax errors: Stuff that's presumably changed in more recent releases. An overridden constructor needs to be deleted, since the thing it overrides no longer exists. Stuff like that. And the source needs to be reformatted. What's with all this C#-like source formatting anyway? Sheesh, this is Java, guys. Comments: |
Twitter UpdatesArchives |