i wouldn't use those 2 in production.. What i find strange is that it seems that they have all the code just in jsp files? Because you really change only jsp files to be up and running again? Where is all the business logic? Database layer? Is all the flow control also done in jsp?
On 10/25/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > Did you take a look at > this: > http://www.zeroturnaround.com/blog/javarebel-brings-class-reloading-to-java/ > ? > > Or the reloading wicket-filter? > > Eelco > > 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] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
