[
https://issues.apache.org/jira/browse/TAPESTRY-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547491
]
Kevin Menard commented on TAPESTRY-1896:
----------------------------------------
I think it's a case of confusion. According to the documentation for getPath()
it "Return the path (the combination of folder and file)." It appears to be a
difference between relative and absolute.
FWIW, I actually ran into this problem taking the code from an "Image"
component off the T5 wiki. Undoubtedly that's where I got confused first, but
at least one other has as well. So, adding some extra langage to the javadoc
to disambiguate would probably help.
> 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
> Assignee: Howard M. Lewis Ship
>
> 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]
