wicket is not MVC so the design of your application will be different. what we provide are hooks for you to build on, if you dont want to use them you dont have to. that is the beauty of the design: they are there for you if you need them, and invisible if you dont.


-Igor


On 2/11/06, Timo Stamm <[EMAIL PROTECTED]> wrote:
Johan Compagner schrieb:
> We have now a Security framework (better said security interfaces) inside
> wicket.


I was wondering whether this is really a good idea. Isn't authorization
a responsibility of the model in a MVC application?



Timo


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to