On 4/30/06, Peter Svensson <psvensson@gmai...> wrote:
> This is curiously enough non-trivial in trapestry. All dynamic things you
> want to put in you pages or download have to come from a separate service.
Why would you need a separate service to render a table of img tags?
As for paging in a table, that is covered in the tapestrytables.war
example app. You just need to structure a TableModel object which can
provide img url's 3 at a time to a contrib:table component, I would
think. It will automatically pagify the results. It is a difficult
question to answer without more detail - are the images served via
tapestry or a standard web server. Are the url's in a database, or
are they statically stored on a path somewhere available to your
servlet container, etc?