I don't think I agree with that. MyComponent c = new MyComponent(); c.setModel(foo) wouldn't work for starters, and you can even set models mutliple times. Not to mention the other problems you mentioned in this thread. And finally, it would just invite people to go crazy with this functionality.
But give us a good example of where using the model to determine an access restriction would actually be useful? Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
