You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2023/07/26 13:52:00 UTC
[jira] [Created] (CAMEL-19660) camel-mapstruct: Improve support for Mappers defined as abstract classes
James Netherton created CAMEL-19660:
---------------------------------------
Summary: camel-mapstruct: Improve support for Mappers defined as abstract classes
Key: CAMEL-19660
URL: https://issues.apache.org/jira/browse/CAMEL-19660
Project: Camel
Issue Type: Improvement
Components: camel-mapstruct
Reporter: James Netherton
Assignee: James Netherton
If you define MapStruct mappings using an abstract class, then some unwanted TypeConverters get registered for the equals and wait methods. In the logs you see:
{code:java}
Added MapStruct type converter: long -> void
Added MapStruct type converter: class java.lang.Object -> boolean
{code}
This happens because they pass the DefaultMapStructFinder.discoverMappings check for a single method arg ,but the void return type is checked against Void.class and not the primitive void.class. We should probably just filter out anything with a primitive return type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)