Unable to load new version of jar'd javascript after redeploy
-------------------------------------------------------------
Key: TAPESTRY-2128
URL: https://issues.apache.org/jira/browse/TAPESTRY-2128
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.9
Environment: Mac OSX, Tomcat-5.5.25
Reporter: Josh Canfield
I'm looking at upgrading from 5.0.6 to 5.0.9, after the upgrade I'm getting the
old version of tapestry.js every time I load the page.
I tracked the problem back through the AssetDispatcher, ResourceCacheImpl and
finally the URLChangeTracker. It looks like requests coming in for the css and
js files in the jars are using a url like this:
jar:file:/Users/joshcanfield/workspace/out/exploded/thedailytubeWeb/WEB-INF/lib/tapestry-core-5.0.9.jar!/org/apache/tapestry/default.css
The URLChangeTracker sees that the protocol isn't file and returns 0.
ResourceCacheImpl assumes that the return value is the last update time, and
stores it. Then when AssetDispatcher checks to see if the file has changed
since the date passed in the If-Modified-Since header, it's always going to be
less so it sends a SC_NOT_MODIFIED error back to the browser.
It seems like the right behavior here would be to return the current time, or
even Long.MAX_VALUE
--
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]
