Re: How-to make modelmapper work with 'lazy" collections properly?

[Jonathan Halterman]

Is it the properties on the source object that are being unexpectedly lazy-loaded or the destination side? Maybe you could give some more details on how things are not working as expected.

Cheers,

Jonathan

On Sun, Nov 16, 2014 at 11:51 PM, David Gale <gale....@gmail.com> wrote:

I have a case where I'm mapping JPA persistence entity classes to similar non-JPA classes. Some of the associations (collections) in my JPA model are lazy loaded. Obviously when modelmapper does its mapping it starts to touch these collections and they get fetched immediately. Is there a way how-to preserve laziness in mapped classes as well?

--
You received this message because you are subscribed to the Google Groups "modelmapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modelmapper...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.