Coincidence I am getting this today also Borut. Someone here may be able to give you more advice, but when it happened to me it was because some of the cells in the grid were referencing lazily-loaded attributes (sub-entities) of the entity your grid is paging on. You can either exclude these items using the 'exclude' parameter of your grid, or ensure they are eagerly loaded in your persistence annotations. There may be some equivalent of an OSIV filter available for Tapestry, I am not sure.
Regards, Jim. -----Original Message----- From: Borut Bolcina [mailto:borut.bolc...@gmail.com] Sent: 11 June 2010 16:39 To: List Tapestry User Subject: tapestry-hibernate grid second page Session is closed Hello, after a while I am again coding with Tapestry. This time I have a chance to use Hibernate, Lucene and their bridge Hibernate Search. I created a search component which uses org.hibernate.search.FullTextQuery to search the index. I am using tapestry grid component to display all the results (as described in Forms in Tapestry (Part Two)). The results get displayed just fine, but when I click on the grid pager to display a second page of the results I am getting: Render queue error in SetupRender[Index:grid]: Failure reading parameter 'source' of component Index:grid: Session is closed! org.hibernate.SessionException Session is closed! As I am new to Hibernate, any clue is appreciated. Thanks, Borut --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
