> 1-Has anyone out there had to defend wicket vs. struts and would you > have any resources/links/presentations to pass this way to help in > presenting wicket to our group?
Yeah, a million times now :) Seriously, I think you can find quite a bit googling (use model 2 vs wicket or something) or searching the mailing list. In a nutshell, imho disadvantages of Struts (and all model 2 frameworks like SpringMVC etc) are: * no reuse * no state management (making things like pageable lists etc and self contained components tedious) * no good abstractions (just actions in the scope of requests) * no clean separation of presentation and logic (as with Struts you'd use JSP or something similar) * encourages bad coding practices (lots of hacks needed to get something of any complexity done and coding with actions and page flows is basically back to procedural programming again). etc etc > 3-Objectively, I am also looking for what wicket is weak at. It depends on how familiar you are with Wicket and whether you think the alternatives are better. If you like to script in pages (like you'd do with JSPs) Wicket is probably not for you. More of a taste matter though. Then there's the fact that by default it uses server memory. But that's easy to get around, and imho even if you use stateless pages, forms and links for your whole application with Wicket, which is a less nice and limited way to use Wicket, you'd still have a nicer programming model than, say, Struts. My2c (I can go on for a bit, but out of time now ;) ) 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
