thanks for the hint, it makes more sense now. So there are two parts,
when it comes to assets:
1) Presenting the asset as a proper link to the client (as component
link inside HTML)
2) Getting tapestry to response it when it is requested as URL.
Currently built in as direct context path or ass
Manuel,
look at the AssetDispatcher class. That will clear up a lot of problems,
I think.
Ciao,
Jonathan
On 06/02/2009 00:49, manuel aldana wrote:
hi,
want to create a new asset-type, which makes images available from
filesystem (file:/) to webapp (http:/), but somehow I don't get it...
I
hi,
want to create a new asset-type, which makes images available from
filesystem (file:/) to webapp (http:/), but somehow I don't get it...
I am sure at least some of my assumptions are wrong:
-with Asset framework I can make resources available through tapestry
webapp context (http://xxx ur
