You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/07/27 18:04:18 UTC
[jira] Created: (TAPESTRY-446) Changes to assets are not picked up, even when caching is disabled
Changes to assets are not picked up, even when caching is disabled
------------------------------------------------------------------
Key: TAPESTRY-446
URL: http://issues.apache.org/jira/browse/TAPESTRY-446
Project: Tapestry
Type: Bug
Components: Framework
Versions: 4.0
Reporter: Howard M. Lewis Ship
Assigned to: Howard M. Lewis Ship
Fix For: 4.0
Changing an asset's content should change the URL to the asset (since it incorporates a digest for the file content), as long as caching is disabled. However, the ResourceDigestSource service doesn't register for cache clear notification from tapestry.ResetEventCoordinatory, so the URLs don't change to reflect the new asset URL. Combined with aggressive caching in the client, this means that changes to assets (typically, javascript files) don't show up in the browser.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Closed: (TAPESTRY-446) Changes to assets are not picked up, even when caching is disabled
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-446?page=all ]
Howard M. Lewis Ship closed TAPESTRY-446:
-----------------------------------------
Resolution: Fixed
> Changes to assets are not picked up, even when caching is disabled
> ------------------------------------------------------------------
>
> Key: TAPESTRY-446
> URL: http://issues.apache.org/jira/browse/TAPESTRY-446
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> Changing an asset's content should change the URL to the asset (since it incorporates a digest for the file content), as long as caching is disabled. However, the ResourceDigestSource service doesn't register for cache clear notification from tapestry.ResetEventCoordinatory, so the URLs don't change to reflect the new asset URL. Combined with aggressive caching in the client, this means that changes to assets (typically, javascript files) don't show up in the browser.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org