[
https://issues.apache.org/jira/browse/CAMEL-15518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193100#comment-17193100
]
Claus Ibsen commented on CAMEL-15518:
-------------------------------------
Yeah well its even more special as that is not an annotation currently as it
was a chicken-egg situation as you cant have camel-api generate configurer (you
need camel-api built first).
So they are generated via pom.xml instructions in camel-core-engine. Where all
the configurers are in core camel.
There is a fix in the maven plugin that generate the source as it already has a
fqn=new fqn mapping where you can just say
<class>org.apache.camel.ExtendedCamelContext=org.apache.camel.impl.ExtendedCamelContext<class>
I fixed that and are rebuilding and testing before submitting a PR
> Wong service generated for the ExtendedCamelContext
> ---------------------------------------------------
>
> Key: CAMEL-15518
> URL: https://issues.apache.org/jira/browse/CAMEL-15518
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Priority: Major
> Fix For: 3.6.0
>
>
> The name of the configurer for the the ExtendedCamelContext is wrong as it
> uses the FQCN of the implementation class
> (org.apache.camel.impl.ExtendedCamelContext) instead of the interface one
> (org.apache.camel.ExtendedCamelContext).
> Maybe the @Configurer annotation should allow to set the name of the factory
> file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
