This is a problem of understanding, IMHO. :) Actually, hot deploys are re-deploys. They are just re-deploys of one file. The JSP will be recompiled, a new Servlet class will be generated on the fly and then the page will be updated.
Even so, I agree that the hot deploy you are asking for, is good for what the company wants, but because of Wicket's nature, that can't work in the same way. What you can argue is this: If there's a new version of a JSP page, so it's a new version of the entire website. New version means, usually, redeploy. cheers -- Bruno Borges blog.brunoborges.com.br +55 1185657739 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld On 10/24/07, Mike03 <[EMAIL PROTECTED]> wrote: > > > 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] > >
