This one caught my eye:

The class must be one that Tapestry instantiates (a page, component, or mixin 
class, or a Tapestry IOC service implementation that implements an interface)

I have a done of DAOs that implement an interface and are registered as 
per-thread services and they never reload. Is this only supported in a 
.services package?

Norman Franke
Answering Service for Directors, Inc.
www.myasd.com



On Nov 1, 2012, at 8:03 AM, Bob Harner wrote:

> Go through the troubleshooting section at
> http://tapestry.apache.org/class-reloading.html ... let us know if you
> still have a problem after checking each of those things.
> On Nov 1, 2012 4:39 AM, "Andy Pahne" <a...@sapida.de> wrote:
> 
>> 
>> Hi,
>> 
>> after being forced to work with other web frameworks for quite a while, I
>> am
>> glad to have a Tapestry project again, so I am back!
>> 
>> I set up a fresh project and I am running it with gradle's jettyRun plugin.
>> Unfortunatly I can't get template and class reloading to work.
>> 
>> In my AppModule class I have set:
>> 
>>        public static void
>> contributeApplicationDefaults(MappedConfiguration<String, String>
>> configuration) {
>>                configuration.add(SymbolConstants.FILE_CHECK_INTERVAL, "1
>> s");
>>                configuration.add(SymbolConstants.PRODUCTION_MODE,
>> "false");
>>                configuration.add(SymbolConstants.EXECUTION_MODE,
>> "DevelopmentMode");
>>        }
>> 
>> I am fairly new to gradle, so I am not sure, if this a gradle problem or if
>> I misconfigured T5.
>> 
>> Any help or pointers would be appreciated. Thanks
>> 
>> Andy Pahne
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/template-class-reloading-and-gradle-s-jetty-run-tp5717491.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>> 
>> 

Reply via email to