On 7/26/06, Kevin Fightmaster <[EMAIL PROTECTED]> wrote:
I have a form that submits criteria whose results will display on the same page in a table below the form. The results is a collection of objects (Person Objects) and this objects can also have a collection of Objects (Events). Using hibernate I understand that until I try and access the events they will be populated with "proxies". I've setup a session manager tied to the "pageBeginRender" and "pageEndRender" which opens a hibernate session on the local thread for that request.
This is typically why I don't like pageBeginRender. That's not a good idea to set a session manager on this method. I would suggest to setup the session manager either on a service... My guess is that when you use a Submit, there is a rewinding that occurs, and when you use DirectLink there is no rewinding. With the submit, the page gets "rendered" twice... And since you create a new session manager for each "render" some of you objects are probably attached using the first session manager and they are probably used with the second session manager (on the effective rendering) and that causes a LazyException... I would highly recommend you to use tapernate... I will take care of the management of the session manager... Also it will provide you a datasqueezer which will reattach all the serialized objects on a form. -- Thanks, Henri.
