OK, thanks for the alternative solution hints. They can be always implemented. However, the question is, whether it should work or not (and why), the way I have done it. It seemed to me that it should have worked so, but did not. Any other ideas?
-- iren -----Ursprüngliche Nachricht----- Von: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Gesendet: Sonntag, 15. Februar 2009 12:47 An: Tapestry users Betreff: Re: [T5.0.18] Bug? : Null property problem with the custom component inside a grid 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
