Johan Compagner wrote:
i wouldn't use those 2 in production..
Yeah JavaRebel is supposed to have too much of a performance penalty to use in production. And for development, I think that Wicket is at least as friendly to live coding and updating as anything else in Java. The only caveat is that since Wicket is actually OO you end up adding and removing methods more often, but JavaRebel takes care of that.
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?
Yes I think this comparison is a little off. If the concern is fixing rendering quirks, typos in the copy, etc, you can leave Wicket's template reloader on in production if you want to, right?
To be able to make big changes without downtime, what people really need is a cluster (even if it's just on one box), with or without Wicket.
Nathan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
