[jira] Updated: (WICKET-1835) Incorrect context path when linking to static resources (css/javascript) in a template page

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg updated WICKET-1835:
----------------------------------

    Fix Version/s:     (was: 1.4-M4)

> Incorrect context path when linking to static resources (css/javascript) in a template page
> -------------------------------------------------------------------------------------------
>
>                 Key: WICKET-1835
>                 URL: https://issues.apache.org/jira/browse/WICKET-1835
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-M3
>            Reporter: Les Hazlewood
>            Assignee: Igor Vaynberg
>
> Per this email thread:
> http://www.nabble.com/Linking-to-static-css-files-in-a-template-page-bug--td19481551.html
> This does not work correctly for context relative paths.
> For example, for an application deployed with this url:
> http://localhost:8080/myapp/
> This call in a parent TemplatePage (using page inheritance):
> add( HeaderContributor.forCss( "/assets/css/style.css") );
> should render the following:
> <link rel="stylesheet" href="/myapp/assets/css/style.css" type="text/css"/> 
> But it does not.  It currently renders this (absolute) path:
> <link rel="stylesheet" href="/assets/css/style.css" type="text/css"/> 
> I'm assuming the same thing occurs for JavaScript files contributed in the same way, but I haven't tested that yet.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.