So.. outside the context and classpath.. wow.
So how is that accessed then? Like what would the url point to it and
who would handle it and return something?..
Or is he saying that the clients can access the filesystem directly.. so
just giving them a "file:///........" url is fine.
If that is the case, I already have a UrlAssetFactory that I can post
up. It allows you to create assets with a "url:" prefix, that just
return the url associated with them. Allowing absolute urls :
"url:http://www.google.com/"; or "url:file:///etc/passwd"
Massimo Lusetti wrote:
On Tue, Apr 1, 2008 at 6:32 PM, Fernando Padilla <[EMAIL PROTECTED]> wrote:
Well, I can't remember who wanted this functionality, of being able to
generate assets dynamically. That is actually done through the
AssetSource, which is backed by a list of AssetFactories. So the could
would look something like the following:
@Inject
private AssetSource source;
public Asset getMyDynamicAsset() {
return source.getAsset( null, "context:/blahblah"+blahblah+"blah", null
);
}
Well the asset is actually outiside the context path and outisde the
classpath. The asset is simply on the filesystem.
Maybe you're right in term that this reqeust is too specific but it
could be useful to have a FilesystemAssetFactory configurable via a
Symbol
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
