[
https://issues.apache.org/jira/browse/TAP5-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119697#comment-14119697
]
Jochen Kemnade commented on TAP5-2185:
--------------------------------------
This change introduces problems: First of all, only the classpath and context
asset factories are used to try to find the asset with the incorrect checksum.
Custom asset factories are not taken into account. Also, it creates invalid
context assets (whose resources' existence is not strongly checked) and
redirects to them.
For example, if I request a webjars asset
({{.../assets/webjars/z38d0e672/jstree/3.0.3/themes/default/32px.png}}) with
the wrong checksum, the change redirects me to a non-existing *context* asset
with the same path
({{.../assets/ctx/8cf55101/jstree/3.0.3/themes/default/32px.png}}).
> Problem with the asset checksums and relative paths based on them
> -----------------------------------------------------------------
>
> Key: TAP5-2185
> URL: https://issues.apache.org/jira/browse/TAP5-2185
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Lenny Primak
> Assignee: Thiago H. de Paula Figueiredo
> Labels: month-of-tapestry
> Fix For: 5.4
>
>
> When JavaScript modules reference other (non-tapestry) JS code via relative
> paths,
> or absolute paths that have to be configured, the checksum is preventing
> the other resources from being accessed properly
> Discussion regarding this can be found here:
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Re-5-4-Problems-with-the-asset-checksums-and-relative-paths-based-on-them-td5723366.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
