You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/09/21 19:04:00 UTC

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

     [ https://issues.apache.org/jira/browse/CAMEL-15553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-15553.
---------------------------------
    Resolution: Fixed

> 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: Improvement
>          Components: tooling
>    Affects Versions: 3.4.3
>            Reporter: Vladimir Dobos
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 3.6.0
>
>
> 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)