Ok following situation:
I use version 3.4, cause in the versions above 4 the inheritance-mapping is
The inheritance structure is like this:
c -> b -> a
z -> y -> x
on the classes a and x is a property with the name test (same name !!!)
The problem is, that dozer creates two superClassMaps. One with the
custom-converter declared, one without the custom-converter declared.
If the custom-converter would be executed decides alone the method
Cause this array would be used to process the super-type-mapping. And if
the super-class-mapping of b to y is at the first position, the
custom-converter wouldn't be executed.
A workaround is, to declare the custom-converter also on the b to y
A test-case is provided, but it fails not everytime. Perhaps by you it
fails never. I had a rate of 50% failings (I think the trigger is the
add-method to the set)
I my view this bug has no relation to the bug 1950626
Log in to post a comment.