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 url is then kind of a gateway to the Resource)
-Resource is the real resource (file, other website, relative context
path etc.)
-AssetFactory implementation tells how to map between the resource and
the client-view (-> toClientUrl())
-if everything works fine, the resource is loaded (amongst others
AbstractResource.openStream() loads the contents) and is passed to the
AssetFactory impl
My biggest doubt to my expectations is that for tapestry it should be
very difficult to track the toClientUrl() return value to its own
webcontext, e.g.: how should it know that
http://domain:port/tapestryApp/toClientUrlValue points to
file://d:/srv/images/xxxx? It then would need to handle a lot of URL
redirecting magic internally.
Any other option for making my filesystem pics accessible to the same
domain:host as the tapestry app is running without putting it to one of
the jars or to webapp-context?
thanks a lot.
--
manuel aldana
ald...@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
