Hello Francesco, we use the open session in view filter and have no real problems so far. But what we also do, we define database views for joining the values we need, we do not join very much in hibernate.
Somtimes I have the feeling, that people try to do to much in hibernate and they forget what can be done by the databes itself. If you do not use databes views till now, think about using them and let the databes handel the fetching. Of course this is no soultion that fits everywher ... Max > -----Ursprüngliche Nachricht----- > Von: fdegrassi [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 25. März 2007 10:49 > An: users@tapestry.apache.org > Betreff: Tapestry 4.1.1 and open session in view > > I'm having an hard time coming out with a robust solution for > integrating Tapestry 4.1.1 and Hibernate. > The sample project i'm working on needs to display and edit > beans loaded by hibernate on the service layer; i've set up a > good fetch plan on hibernate that minimizes db access and i'm > pretty happy with it, and until now i manually initialized > the lazy collections and references needed by the view before > passing them to the presentation layer (Tapestry). > This is hard to do, because different pages need different > data from the beans, and i end up initializing all of the > properties and collections (the object graph is pretty deep > and complex). > I was thinking of using the "Open Session in View" approach, > but it turns out it does not work very well with Tapestry > because of the heavy use of serialization in session and in > page of objects, so frequently i get problems with > deserialized objects not bound anymore to the current session. > I looked at Tapernate and at Honeycomb, both address the same > problem, both have really scarce documentation and both seem outdated. > I would really appreciate your expert feedback on this issue. > > Should i use tapernate ? > Should i try Honeycomb ? > Should i keep manually initializing my objects ? > > Thanks in advance for your help. > > Francesco > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
