See the last comment on the issue
Since this is fixed by clearing the browser cache, I'm marking this as
resolved. If anyone feels strongly that Tapestry should have a better
mechanism for preventing old JavaScript from hanging around after an app is
upgraded to a newer Tapestry version (such as h
Thanks Lance for taking a look into the problem.
Is clearing the browser cache, only solution to this problem ?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/problem-while-submitting-the-form-tp5659515p5659673.html
Sent from the Tapestry - User mailing list archive at
Try clearing your browser's cache
See the jira for TAP5-1777