We've always added "-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true", something doesn't work properly if we don't, but that was all done over 2 years ago. The dev environment hasn't changed, but with T5.2.0 Live class reloading no longer works.
Igor, does live class reloading work properly for you using runjettyrun and T5.2.0? I'd imagine for small sites it wouldn't be very easy to notice, but for us when we change something (component or page) there's a fairly lengthy pause the next time a page is requested. Do this a couple of times, and permgen space is quickly exhausted. I'm hoping that the a global service reloading switch will be provided so we can turn that off and see if we can get components & pages reloading as before with T5.0 & T5.1 Thanks, Andy. > -----Original Message----- > From: Igor Drobiazko [mailto:igor.drobia...@gmail.com] > Sent: 06 October 2010 18:44 > To: Tapestry users > Subject: Re: [T5.2] Live class reloading not working with jetty > > I'm using run-jetty-run and there is no need for any configuration. > Just > install it and start your web app. The only problem is that JNDI is not > supported. > > On Wed, Oct 6, 2010 at 11:35 AM, Christian Köberl < > tapestry.christian.koeb...@gmail.com> wrote: > > > > > I think RunJettyRun is also a fork of Jetty Launcher (but I'm not > sure). > > With RunJettyRun you have to add > > "-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true" to make > Tapestry 5 > > work (see > > > http://wiki.apache.org/tapestry/Tapestry5HowToSetupEclipseRunJettyRun). > > > > > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
