Thanks for the heads up; I think I know why this is behaving as you suggest, and its fixable. Add an issue.
Basically, when using reloadable, the object at the end of the delegate/advice stack, which is normally the service implementation, is itself a proxy that performs live class reloading. Currently, it does not attempt to load the service implementation until needed, but that can and should be changed, giving reloaded services that same semantics as non-reloadable services (just with one extra level of proxy). On Wed, Mar 24, 2010 at 2:27 PM, Christophe Cordenier <christophe.corden...@gmail.com> wrote: > Hi > > .eagerload() does not work when we do not call preventReload() on the > service. > If it's by design, maybe the first call to one of the two methods should > take the priority, or maybe an exception should be thrown if the two are > called on the service. > > Best Regards, > Christophe Cordenier. > > 2010/3/13 Howard Lewis Ship <hls...@gmail.com> > >> As you may have seen from my blog posting, I just added live service >> reloading to Tapestry 5.2. I'd encourage users to give 5.2 a whirl >> and make sure that the changes I've made work across different >> platforms and servlet containers, and that there is no performance >> impact. >> >> As with pages and components, live service reloading is only for >> service implementations whose class files are on the file system. >> >> This means that services from third party JARs will operate exactly >> the same as in 5.1. >> >> Further, in a production environment, the classes will be packaged up >> into a WAR (or even a JAR inside the WAR) and should, again, operate >> exactly as with 5.1. Live service reloading exists to accelerate >> development, and boy does it! >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > > -- > Regards, > Christophe Cordenier. > > Developer of wooki @wookicentral.com > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
