You should be able to point Jetty at your workspace's src/main/webapp folder (or equivalent). As long as your IDE compiles classes to folders on Jetty's classpath, live class reloading just works.
Live class reloading is only for class file directly on the file system; classes packaged into JARs are not subject to live class reloading. The most likely problem is that your classes are compiled to directory A but not then copied to directory B which is on Jetty's search path. I've had zero problems with live class reloading in Eclipse and IntelliJ, but I haven't tried NetBeans. On Tue, Oct 28, 2008 at 12:41 AM, Ville Virtanen <[EMAIL PROTECTED]> wrote: > > Hi, this is almost off topic... > > but atleast we have, and have always had problems with live reloading. There > are less than 10 developers currently that are familiar and working with T5 > here and not single one currently has working live reloading. > > It would be great if there would be detailed how-to live reload document, > that clearly explains what conditions must be met prior live reloading > works. > > - Ville > > Ps. We have NetBeans 6.1 + jetty, tomcat 6 or glassfish with either ant > build process or maven depending on the project. > > > Thiago H. de Paula Figueiredo wrote: >> >> Hi! >> >> Tapestry 5's live class reloading is a huge productivity boost, specially >> when compared to almost any other web framework out there. Maybe 90% of >> all web app reloads are eliminated. >> >> But there is the remaining 10% of the reloads. Most of them are related to >> new pages and components. In other words: Tapestry does not pick new >> pages, components and templates after it is started. If this fact is >> reversed, we could develop an entire web interface without reloading the >> application. >> >> In addition, there is one other reason to implement this new feature: >> applications with static content. Every time I add a new page to my >> website, www.arsmachina.com.br, I have to restart the application, as it's >> written on T5. This is not an issue to arsmachina.com.br, but can be to >> high traffic websites. >> >> What do you think about this? I've just created it: >> https://issues.apache.org/jira/browse/TAP5-315 If you agree with me, >> please vote. :) >> >> PS: My website does not have any interactivity, any logic yet. Just static >> content. My website is implemented with T5, so I can use the Layout >> component pattern and not repeat the pages' common parts (header, footer, >> menu) on every page. T5 can be very useful even in static websites. :) >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java consultant, developer, and instructor >> http://www.arsmachina.com.br/thiago >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/New-JIRA%3A-Tapestry-does-not-pick-pages%2C-components-and-templates-after-application-startup-tp20198999p20202575.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]