I have several in-production apps that use that stack. Specifically, what kind of lazy initialization problems are you seeing? Lazy initialization problems are almost always caused by a closed session. One good pattern for solving that problem is using the Open Session in View pattern. Spring has a Servlet filter that implements the pattern and is very easy to use. I use that all the time.
The lazy initialization problem is also caused by detached objects, which can happen VERY easily in Tapestry thanks to all the persistence options available. For example, Hibernate objects can become detached when a collection is iterated on a FormTable and you don't use an IPrimaryKeyConvertor. The result is that the Hibernate objects get serialized out as hidden fields on the page. If you use one of those values in an event handler it will be detached and lazy properties will throw exceptions. This is just one example. There are plenty of other ways to get detached objects. Describe your problem more specifically. Perhaps somebody will have seen the exact problem before. -----Original Message----- From: Derek Brown [mailto:[EMAIL PROTECTED] Sent: Friday, September 16, 2005 5:25 PM To: Tapestry users Subject: Tapestry, Spring and Hibernate This has been discussed on the list many times but I have not seen a definite answer, does anyone have a working solution to enable lazy initialization with Spring, Hibernate and Tapestry? Sample code would be greatly appreciated. Thanks __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com --------------------------------------------------------------------- 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]
