[ http://issues.apache.org/jira/browse/TAPESTRY-655?page=all ]
Howard M. Lewis Ship updated TAPESTRY-655:
------------------------------------------
Summary: In some circumstances, using the classpath: or context: prefixes
on paths fails to work (was: ClasspathAssetFactory assumes that passed base
resource is ClasspathResource)
> In some circumstances, using the classpath: or context: prefixes on paths
> fails to work
> ---------------------------------------------------------------------------------------
>
> Key: TAPESTRY-655
> URL: http://issues.apache.org/jira/browse/TAPESTRY-655
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Reporter: Vjeran Marcinko
> Assignee: Howard M. Lewis Ship
>
> When one wants to reference "classpath:" asset, BUT inside specification that
> is specified as "context:" base resource, ClasspathResourceFactory assumes
> that passed baseResource is of same "classpath" prefix.
> Thsi is frequent case when foo.application is located under /WEB-INF
> ("context:" base resource), and page's specification path is specified with
> "classpath:" inside <page> element.
> Here is snippet from ClasspathResourceFactory :
> public IAsset createAsset(Resource baseResource, String path, Locale
> locale, Location location)
> {
> Resource asset = baseResource.getRelativeResource(path);
> Resource localized = asset.getLocalization(locale);
> .......
> return new PrivateAsset((ClasspathResource) localized, _assetService,
> location);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
