tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2185) Problem with the asset checksums and relative paths based on them
Date Wed, 03 Sep 2014 21:02:51 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120446#comment-14120446
] 

Thiago H. de Paula Figueiredo commented on TAP5-2185:
-----------------------------------------------------

I forgot to mention: my fix could be improved by checking asset.getResource().exists() before
returning the asset.

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

Mime
View raw message