[
https://issues.apache.org/jira/browse/CAMEL-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-15183.
---------------------------------
Resolution: Fixed
> camel-main - Exclude Abstract Classes From Package Scanning
> -----------------------------------------------------------
>
> Key: CAMEL-15183
> URL: https://issues.apache.org/jira/browse/CAMEL-15183
> Project: Camel
> Issue Type: Improvement
> Components: camel-main
> Affects Versions: 3.3.0
> Reporter: Dixon Whitmire
> Priority: Major
> Fix For: 3.4.0
>
>
> My team is developing a "stand-alone" Camel Main application which utilizes
> route builder discovery using the package scanning feature. The [current
> implementation|https://github.com/apache/camel/blob/master/core/camel-main/src/main/java/org/apache/camel/main/BaseMainSupport.java#L409]
> 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|https://github.com/apache/camel/pull/3911] updates the package
> scanning algorithm and the corresponding test case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
