[jira] [Comment Edited] (CAMEL-15553) camel-component-maven-plugin issue adding configuration bean to component subclass

["Claus Ibsen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-15553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198389#comment-17198389 ] 

Claus Ibsen edited comment on CAMEL-15553 at 9/18/20, 3:03 PM:
---------------------------------------------------------------

You should use this goal for 3rd party components
org.apache.camel.maven.packaging.GenerateComponentMojo

That said there may still be some limitations or something we dont yet support for what you do.


was (Author: davsclaus):
You should use this goal
org.apache.camel.maven.packaging.GenerateComponentMojo

> camel-component-maven-plugin issue adding configuration bean to component subclass
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-15553
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15553
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 3.4.3
>            Reporter: Vladimir Dobos
>            Priority: Minor
>
> I'm subclassing camel-jms component and need to add additional configuration bean with some uri parameters.
>  Unfortunately, when generating configurers, the plugin creates only one getOrCreateConfiguration method (for parent JmsConfiguration bean) in component configurer and tries to reference parameters within my additional configuration bean using this method, creating invalid java code. I was able to circumvent this by adding parameters directly to my subclassed component, but this is ugly and adds unnecessary code to component (also cannot reuse the configuration bean in subclassed endpoint). Below is link to example component demonstrating the issue:
>  [https://github.com/vdobos-tr/camel-maven-plugin-issue]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)