Configure Moo to Update Mismatched Classes

[geoffreywiseman]

By default, if Moo is doing an update/translate and finds an object that doesn't match what it itself would have put there, it will replace the object with a new object derived from translation.

There many be a reason why someone might prefer Moo to update the object already in place, even if that object's class isn't the same as the class of the object Moo might have used. For instance, this approach would be better when dealing with Hibernate properties that might be proxied.

There are options here in terms of how Moo might be configured and what you might need to tell Moo to get it to do what you want. I'm not sure i'll need most of these options.