Ability to load unread properties after deserialization

[GoogleCodeExporter]

What version of the MyBatis are you using?
3.0.5-SNAPSHOT

Please describe the problem.  Unit tests are best!
Enhanced solution of Issue 110 & Issue 200. ResultLoaderMap$LoadPair has the 
ability to survive de/serialization for some (most?) cases.

Preconditions are:
 - User is required to provide a factory class which returns connection that will be used to load properties after deserialization.
 - Parameter of mapped statement has to serializable.

Should be backward compatible because when a unread property is accessed after 
deserialization and these extra requirements are not met, ExecutorException is 
thrown.

I had to @Ignore some tests in SerializableProxyTest as they don't provide some 
information that are available (at least I think so) during standard execution 
(MetaObject and ResultLoader).

Original issue reported on code.google.com by me...@rewor.cz on 6 Apr 2011 at 12:56

Attachments:

• mybatis-lazy_deserialize.patch