Ok, I had just a look at the Swarm home page, and didn't go further, but promise I will look at it deeper, now I know it's simple.
Swarm is designed to be plain and simple. In short this is what you need to do: 1 implement Principal (i could see about a reasonable default implementation , but my guess is you want to store this in a database anyway and i am not sure i want a dependency on jpa) 2 create policy files 3 implement WaspApplication (by extending SwarmApplication) Off the top of my hat, that is al you need to get the default running. Off course if you want something special you need something more, but where don't you need to do that. But if you feel we could improve on some areas, let me know. Maurice On Nov 6, 2007 10:35 PM, <[EMAIL PROTECTED]> wrote: > I wished to try the basic Wicket authentication because it looked plain > simple (and simplicity and fewer code is my mantra!) > I had seen the Swarm one, but it didn't look as straightforward. Maybe I > will give it a try if I can't go with the standard one. > > Regards, > Hugues > ----- Regards, Hugues -- View this message in context: http://www.nabble.com/Problem-with-wicket-authentication-tf4751663.html#a13635200 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
