In Tapestry, for component classes, you can make any change you want. On Wed, Oct 29, 2008 at 2:52 PM, Martin Strand <[EMAIL PROTECTED]> wrote: > On Wed, 29 Oct 2008 22:42:50 +0100, Kalle Korhonen > <[EMAIL PROTECTED]> wrote: > >> On Wed, Oct 29, 2008 at 3:32 PM, Thiago H. de Paula Figueiredo < >> [EMAIL PROTECTED]> wrote: >> >>> Just to provide a differing viewpoint: I've had live class reloading >>>> >>>> already in Tapestry 4.x with Tomcat, Eclipse and Sysdeo's Tomcat plugin >>>> for >>>> years. I've always wondered what the fuss is about live class reloading >>>> as a >>>> new >>>> feature. >>>> >>> AFAIK, what they do is to restart the application context everytime you >>> change a class. >>> T5's live class reloading is about not restarting the context when you >>> change a class. >>> >> >> No, this is live class reloading. I do know the difference between context >> reloading and hot code swapping. >> >> Kalle > > I wouldn't be able to live without hot code swapping. Unfortunately it only > works as long as you don't add new public methods or make other large > changes. Add your votes here! :) > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4910812 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
