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 (Commented) (JIRA)" <ji...@apache.org> on 2011/10/24 17:47:34 UTC
[jira] [Commented] (TAP5-1016) unable to locate static asset if
folder name contains a '.' character
[ https://issues.apache.org/jira/browse/TAP5-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134167#comment-13134167 ]
Howard M. Lewis Ship commented on TAP5-1016:
--------------------------------------------
Is this still an issue under 5.3? Much of the 5.2 code has been rewritten for 5.3.
> unable to locate static asset if folder name contains a '.' character
> ---------------------------------------------------------------------
>
> Key: TAP5-1016
> URL: https://issues.apache.org/jira/browse/TAP5-1016
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.2
> Reporter: Jim Smart
> Priority: Minor
>
> i have just upgraded from tapestry 5.1.0.5 to 5.2.0-snapshot (using the version 5.2.0 snapshot in the maven repository)
> i have found a minor regression...
> in 5.1.0.5 the following line would work ok:-
> <link href="${context:my.folder.name/some.css}" rel="stylesheet" type="text/css"/>
> ...but under the version of 5.2.0-snapshot that i am running, this produces a (behind the scenes) 404 when the page tries to load the css in question (resulting in an un-styled page), although the created url looks fine to me.
> i have narrowed down the issue to this:-
> if i remove the '.' chars from the folder names (ie. change 'my.folder.name' to 'my-folder-name', or similar) then 5.2.0-snapshot is fine with the path -- otherwise it seems to simply pretend that the files in question don't exist... :-/
> fwiw, having extra dots in the filename (eg. my.test.css) works ok, the problem only seems to be with folder names.
> the same problem applies to images also, not just css files - is it a bad regex somewhere in the new asset protection code maybe?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira