As for your problem with debugging. Tapestry transforms your component classes such that they no longer read/write to member variables in your class. Instead, getters and setters are generated that are backed by a thread local.
When running in development mode, tapestry helps out the developer by mirroring the field values to the component fields to make life easier for you when debugging. I'm guessing that you are running in production mode. http://tapestry.apache.org/configuration.html#Configuration-tapestry.productionmode -- View this message in context: http://tapestry.1045711.n5.nabble.com/select-event-handler-wont-hit-breakpoint-quarky-runtime-came-back-tp5717846p5717854.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
