atos1990 / orika

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

Inheritance mapping with customized mapper - custom mapper not fired for parent class #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run the attached JUnit test

What is the expected output? What do you see instead?
The object should map flawlessly, yet the customized mapper for parent class is 
not fired.

What version of the product are you using? On what operating system?
orika-core 1.0, JDK 1.5

Please provide any additional information below.

Original issue reported on code.google.com by lighteater on 8 Mar 2012 at 11:01

Attachments:

GoogleCodeExporter commented 9 years ago
Attaching the same customized mapper to each subclass classmap does the trick, 
but it's an inconvenient workaround :) 

Original comment by lighteater on 8 Mar 2012 at 11:05

GoogleCodeExporter commented 9 years ago
There's a fix for this case in the new 1.1-generics branch. It should make it 
into the next release.

Original comment by matt.deb...@gmail.com on 9 Mar 2012 at 8:16

GoogleCodeExporter commented 9 years ago
Thanks

Original comment by lighteater on 9 Mar 2012 at 8:30

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
(was fixed in 1.1.0 release)

Original comment by matt.deb...@gmail.com on 4 Aug 2012 at 5:06