> Just make sure whatever you send through LCDS over the wire is not > lazily loaded. So load all collection explicitly with hibernate before > you send them. Or better yet don't send hibernate objects of the wire > at all, create DTO (Data Transfer Objects; search for DTO design > pattern) objects instead. Load everything you need in your flex > application into the DTO and send that over to your flex app. > > gr > marcel
Or catch the errors and work through the problem, perhaps extending your collections to solve for the item pending errors. DTO/VO are synonymous patterns. Half the beauty of using hibernate as a solution is the potential for lazy loading your object graphs. It >is< most certainly a flex problem, and can be solved by many different approachs, as the op's posted solution demonstrates. While 'just don't do it' is certainly a simple solution, it is hardly adequate. I'd love to see a useful response to this, as I am working through it right now myself.
