On Wed, 2007-05-30 at 13:44 +0700, Ted Steen wrote: > Somewhere in the documentation it says that all pages are components, > so i guess that all components and pages (that are special kinds of > components) will automatically reload. Then the question is what's required to get it to work.
For me changed classes are not picked up automatically, when running mvn jetty6:run... If it's working for you, what's your setup, or did you do anything special to support class reloading? Is it connected with a context reload of your servlet container (what AFAICS should not be necessary)? Thx && cheers, Martin > > > 2007/5/29, Martin Grotzke <[EMAIL PROTECTED]>: > > Hi, > > > > is the class reloading in T5 limited to component classes as > > described at > > http://tapestry.apache.org/tapestry5/tapestry-core/guide/component-classes.html: > > "However, class reloading only applies to component classes." > > > > Although, at > > http://tapestry.apache.org/tapestry5/tapestry-core/guide/reload.html is > > written that "In Tapestry 5, page and component classes will > > automatically reload when changed"... > > > > Of course, the latter case would be really, really cool and appreciated, > > but if so: how do I get it to work? > > > > Thx && cheers, > > Martin > > > > > > > > > > -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
