Quoting Dale Becker <[EMAIL PROTECTED]>: > I have tried managing the session across requests using the Spring > "OpenSessionInView" Filter but that does not help as Tapestry pages keep > around object references that were loaded during previous requests. > > If some part of the object graph is lazily loaded, it isn't always possible > to reattach it to the current session, because there is not enough > information in the proxy, this is the case for example with a polymorphic > class.
This is a common problem. To avoid this problem, we either only store the ids of the objects or reload the objects according to their id if needed. Ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
