atos1990 / orika

Automatically exported from code.google.com/p/orika
0 stars 0 forks source link

resolveSourceType does not distinguish by destinationType #45

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Create a situation where a single source type is mapped to more than one 
destination type over a period of time.
If explicit mappings are not registered, then the resolved source type can be 
different depending on the order in which the auto-mappings are triggered.

What is the expected output? What do you see instead?
The same source type should be resolved regardless of the order in which 
auto-mappings are triggered.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by matt.deb...@gmail.com on 5 Sep 2012 at 11:01

GoogleCodeExporter commented 9 years ago
Test case to follow...

Original comment by matt.deb...@gmail.com on 5 Sep 2012 at 11:02

GoogleCodeExporter commented 9 years ago
See attached test case; issue has since been corrected in 1.2.0 branch by 
removing 'resolvedTypes' from MapperFacadeImpl

Original comment by matt.deb...@gmail.com on 6 Sep 2012 at 4:32

Attachments:

GoogleCodeExporter commented 9 years ago
Fixed in 1.2.0 release

Original comment by matt.deb...@gmail.com on 7 Sep 2012 at 9:56