Personally, I tend to treat large, dynamic collections of images as though they are stored on some other server, since many apps will find that such collections may require things like a content delivery network in order to efficiently deliver them to users as the collection grows. So I write a component that knows how to construct the <img> tag correctly when given the path to the file. Then I just use that component and look up the path in the db and pass it to the component via an ognl expression. Initially, the URL in the img tag may be to the same server, but if I have to move it later, that is trivial to do. I've never tried to solve this problem using an actual tapestry IAsset.
--sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
