Paths wrong for context assets in root context.
-----------------------------------------------
Key: TAPESTRY-1896
URL: https://issues.apache.org/jira/browse/TAPESTRY-1896
Project: Tapestry
Issue Type: Bug
Components: Framework
Affects Versions: 5.0.6
Environment: Java 5, MacOS X 10.5, Jetty 6.1.
Reporter: Kevin Menard
Calling asset.getResource().getPath() on a context asset in a webapp mapped to
the root context yields an incorrect path. The path does not have the leading
"/", which represents the context. As a result, linked in assets (e.g., CSS or
images) will work fine if at the root level of the webapp, but if you go down
to a deeper level, the asset path doesn't work and Tapestry thinks you're
trying to load in non-existent pages.
When mapped to any other context, there is no problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]