[
https://issues.apache.org/jira/browse/TAP5-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693613#action_12693613
]
manuel aldana commented on TAP5-423:
------------------------------------
Because of supporting multiple roots I am thinking how to map this to syntax:
1)
//mapping it to the path itself (fs1 as a symbol needs to be defined in
configuration where it should point to)
@Path("filesystem:/fs1/asset.txt")
private Asset filesystemAsset;
vs.
2)
//mapping to the context type (filesystem1 needs to be defined in configuration)
@Path("filesystem1:/asset.txt")
private Asset filesystemAsset;
I would prefer option 1). is more consistent to the other asset types context +
classpath.
> Implement a file-system Asset type
> ----------------------------------
>
> Key: TAP5-423
> URL: https://issues.apache.org/jira/browse/TAP5-423
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.18
> Reporter: manuel aldana
>
> currenty it is built in to retrieve assets from classpath and from webcontext.
> a file system asset type which can retrieve stuff directly from the
> filesystem (e.g. from /srv/statics/xxxx) makes also sense.
> something like:
> *ResourceFileSystem extends AbstractResource* and *FileSystemAssetFactory
> extends AssetFactory*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
