[CAMEL-15183] camel-main - Exclude Abstract Classes From Package Scanning

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.4.0
• Component/s: camel-main
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Dixon Whitmire
• Created: 13/Jun/20 02:28
• Updated: 13/Jun/20 12:57
• Resolved: 13/Jun/20 07:18

Description

My team is developing a "stand-alone" Camel Main application which utilizes route builder discovery using the package scanning feature. The current implementation instantiates any class within the package which extend RouteBuilder. If an abstract class which extends RouteBuilder is in the package, the Camel Context fails to load since the abstract class cannot be instantiated.

Our application currently utilizes an abstract class within a "scanned" package, so we wanted to see if the scanning algorithm could be updated to exclude abstract classes.

This PR updates the package scanning algorithm and the corresponding test case.

Issue Links

• relates to: CAMEL-15184 PackageScan.findImplementation - Should filter out abstract classes
• links to: GitHub Pull Request #3911