What exactly are the issues with Tapestry and Lazy Loading? I've been using hibernate and tapestry extensively and have not run into any lazy loading issue. I really don't see anything in Tapestry that would make lazy loading any more of an issue than it is in any other web framework. It all really comes down to how you handle your hibernate session using the patterns discussed in the hibernate documentation such as session-per-request or session-per-conversation. At what point do you actually get lazy loading problems?
On 11/3/06, Bill Holloway <[EMAIL PROTECTED]> wrote:
I've seen recently some criticism of Tapestry in terms of using Hibernate. Problems with lazy loading. I know Tapernate is out there, but the docs are pretty thin. I'm using the threadLocal version of the much-documented HibernateUtil in a DAO layer. Going well. What will Tapernate actually do for me? Does it really solve the lazy-loading problem? Are there decent docs? I would HATE to have to abandon tapestry to work around performance problems falling out of non-lazy-loading. Thanks, Bill --------------------------------------------------------------------- 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]
