Many thanks for all replies. This will help me get the decision makesr to
give Wicket a try.
Dave
--
View this message in context:
http://www.nabble.com/Enterprise-application-using-Wicket-t1420394.html#a3852549
Sent from the Wicket - User forum at Nabble.com.
What argument *couldn't* be made? Comparing JSP and Wicket is like night and day...JSP is antiquated technology in comparison.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
Dave,
Wicket has built-in hooks to facilitate its use in large, multi-server
configurations where load balancing and other scalability considerations
are required. You are on pretty solid ground.
I cannot speak from experience about how Wicket handles more than 10 or
20 concurrent
JSP is not included, but here:
http://www.virtuas.com/articles/webframework-sweetspots.html is a
discussion that might help.
Eelco
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
