I am trying to use lazy loading in Tapestry 3.0.3 and cannot get it to work.
I have in the meantime made my object model use join="fetch" to get the sub-objects data (which affectively disables lazy loading). But this means our application loads large amounts of data when it is not needed. This is all ok when dealing with one instance of an object as the object graph is not too bad for one object - the problem arises when we do searches. When doing a search the system might be loading a few thousand instances of that large object graph. Which causes major performance issues for us. 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. Can anyone shed some light on this for me - I desperately need to get this working.
