On Sun, Feb 15, 2009 at 8:21 AM, Otho <taa...@googlemail.com> wrote: > One possible solution is to store the images in the filesystem instead of > the database and store only the filename in the db from where you can > construct a path. But I think that isn't compatible with your requirements?
Maybe a better solution would be to provide an Asset binding (like context and classpath) and AssetFactory, both pulling the images from the database. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
