I'm running into some trouble w/ the live class reloading feature (the template reloading works fine), tested both on Tomcat 6 , Glassfish 3 Prelude, and Glassfish V2 (all three servers support exploded war deployment). If I re-deploy the application in these servers, then I get the new version of the class. Everything works if I'm running it in Jetty (mvn jetty:run).
Here's what I do ( I use NetBeans to go through these steps): * Create a new project based on a quickstart archetype * Changed the <archiveClasses> option in the war goal to false so that re-deploying to the app server doesn't fail with the "manifest not found problem" * I run the app. I can successfully reload the Index page and it works OK. Now, for testing the live reloading. Using the war:exploded target, I can have the app running on the server, and without re-deploying the app in the server, I can update the .tml files and the class files inside of the target/app-name directory. However, T5 doesn't seem to pick up the class changes neither in Tomcat nor in Glassfish. Interestingly enough, after I run "mvn compile war:exploded", the next time I refresh the page, I see some T5 output on the console indicating that the class is being transformed. However, the output of the Index.class is the same as with the old version of the class. Any ideas about why this might be so ? Is anyone else developing on something other than Jetty to confirm that the live class reloading works for them ? -- View this message in context: http://www.nabble.com/Live-class-reloading-problems-tp20594857p20594857.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]
