[
https://issues.apache.org/jira/browse/TAP5-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-4.
-----------------------------------
Resolution: Fixed
Fix Version/s: 5.0.16
> Document the need to version classpath assets to prevent unwanted client
> browser caching
> ----------------------------------------------------------------------------------------
>
> Key: TAP5-4
> URL: https://issues.apache.org/jira/browse/TAP5-4
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.0.15
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Trivial
> Fix For: 5.0.16
>
>
> Because Tapestry now encourages the client browser to cache classpath assets
> (including tapestry.js, etc.) it is important that when upgrading from one
> snapshot to another, the browser cache be cleared. It is also possible, in
> FF, to use shift-reload to force a reload of everything on the page.
> Otherwise, Taepestry components will references JavaScript functions that do
> not exist, since the browser is holding on to the older version of the
> tapestry.js file (because the version number does not change between
> snapshots).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]