Congratulations!, is this true also for Spring injected services or only for those managed with Tapestry IOC?
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 > > -- Raul Raja
