Which hibernate adapter should be used to handle Lazy Initialization in BlazeDS / Spring Flex integration projects?

Question

I will explore the ways in which Spring Framework, Hibernate, and BlazeDS can play happily together without throwing lazy initialization exceptions.

So far I have come across Gilead, dpHibernate, and a completely different alternative implementation of this problem using the GraniteDS Tide platform.

Apart from GraniteDS, it seems that there is not much documentation on the proper integration of dpHibernate or Gilead.

Are there alternative libraries that solve this problem? Where can I find the best guides to integrate these lazy boot libraries with the Spring-Flex integration project?

Answer 1

I usually translate my entities into DTO and then migrate them.

Answer 2

I see this question a couple of years, but I'm going to answer with the hope that it helps someone stumble about this from google:

Take a look at the dozer . As much as I hate DTO, this is a good system for matching Entity Objects with DTOs with control over what is being copied.

Answer 3

. Tide, GraniteDS.

Answer 4

I use Gilead in my current project and it works very well once it is configured correctly. This configuration can be found on the gilead project website. If everything works well, you should start Gilead immediately. I can’t speak outside the box, though, but with Gilead you don’t have to adapt your javabeans or your services or anything else. Just a simple configuration in remoting-services.xml