Hi, I'm at a new job that has a very ugly JSP presentation layer and I'm
really missing Wicket.  I think I can make a solid case for moving to Wicket
except for the issue of hot deploy.  On the development side, a server
restart takes about 2 minutes so they need the hot deploy of JSP code for
rapid development.  On the production side they want to maximize uptime.

Is there any way to address this concern with Wicket?

Thanks!
Mike
-- 
View this message in context: 
http://www.nabble.com/hot-deploy-new-updated-components--tf4687796.html#a13397603
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to