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/10/30 16:56:00 UTC

[jira] [Commented] (CAMEL-15778) camel-main - Optimize and clear main configuration configurers after started

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

Claus Ibsen commented on CAMEL-15778:
-------------------------------------

We can have configurers marked as bootstrap = true for those in camel-main etc and then we can make it easier to clear only bootstrap, and leave the components as-is. But if the user dont have any dynamic endpoints / components (such as not using toD, recipient list) then they can clear those as well

> camel-main - Optimize and clear main configuration configurers after started
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-15778
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15778
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.7.0
>
>
> After camel-main has started up, then its own configurer for configuring camel.main.xxx are no longer in use, and we can clear their state (it has an ALL_OPTIONS) map that has data that can be cleared.



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