Tapestry transforms page / component classes so that at runtime, the values are written/read from a thread local map and the fields are no longer used.
In development mode, tapestry mirrors these values to the fields to make your life easier when debugging. I'm guessing that you are debugging a tapestry app running in production mode. Try switching to development to benefit from easier debugging and also live class reloading. http://tapestry.apache.org/configuration.html#Configuration-tapestry.productionmode -- View this message in context: http://tapestry.1045711.n5.nabble.com/quarky-page-injection-late-allocation-tp5717448p5717453.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
