Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-4

Document the need to version classpath assets to prevent unwanted client browser caching

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • 5.0.15
    • 5.0.16
    • None
    • None

    Description

      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).

      Attachments

        Issue Links

          is part of

          New Feature - A new feature of the product, which has yet to be developed. TAP5-41 Create a guide to creating and packaging component libraries

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              hlship Howard Lewis Ship
              hlship Howard Lewis Ship
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: