you really should not reference hibernate entities directly. use a loadable detachable model for that.
otherwise when the page is deserialized the entity is detached from the session... -igor On Mon, Feb 14, 2011 at 8:23 AM, Alexandru Artimon <aarti...@dgfoundation.org> wrote: > Hello, > > I'm having some problems in porting our application to Wicket. > > Wicket Serializable Checker tries to see if all the fields in a hibernate > bean are serializable, but some of the fields are collections that have lazy > set to true. Now, at the moment it tries to check those collections the > session is closed and thus a "failed to lazily initialize a collection" > exception arises. If the session was open then this checker will probably > initialize all the lazy collections recursive and will make the lazy setting > useless. > > In order to avoid this problem I started setting the "lazy collection" > fields to transient in the POJOs, which doesn't affect saving it with > hibernate. But I realize we have a lot of collections with lazy true. > > Is there some elegant solution? Maybe like turning the Serializable Checker > off? > > Thanks, > Alexandru > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
