The fact that you can be many more times productive and simultaneously produce clean, manageable code is probably the top-most incentive for using Wicket.
A con might be the fact that session-state is used rather heavily. However, in my own benchmarking...Wicket holds up extremely well w/ 100's of simultaneous users (that was while testing Wicket 1.1.1 & Hibernate, pulling up several different types of object graphs.)
Just my 2c...
-v
On 4/9/06, dave723 <[EMAIL PROTECTED]> wrote:
The Fortune 50 company where I work is migrating a proprietary web
application and is tending toward JSP.
I'd like to get them to consider Wicket. What persuasive arguments can I
make that would counter the momentum of JSP? Thanks.
--
View this message in context: http://www.nabble.com/Enterprise-application-using-Wicket-t1420394.html#a3828769
Sent from the Wicket - User forum at Nabble.com.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
