hi wicket folks,

in my last wicket projects i used wicket-auth roles and swarm/wasp. i think
swarm/wasp is a really good base for larger web-applications. but we all know
about the problem with swarm/wasp. i developed a few extensions for swarm, but
its a lot of code and so nobody starts to maintain and whats more important to 
develop. so wasp swarm stops on wicket 1.3.

there was plans to integrate wicket-security in 1.5. @wicket developers: is this
still relevant?

i think we will not find one person who develops wicket-security allone - so
who's interested?
its not the part brings the most fun in wicket development area but a very very
important part of every enterprise application - so contribute! lets define a

regards alex

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to