camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-9924) Consider keeping custom add components in camelcontext when stopped so people can start again
Date Sun, 29 May 2016 06:40:12 GMT

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

Claus Ibsen resolved CAMEL-9924.
--------------------------------
    Resolution: Won't Fix
      Assignee: Claus Ibsen

> Consider keeping custom add components in camelcontext when stopped so people can start
again
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-9924
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9924
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>
> See CAMEL-9916
> If people restart manually using stop/start then Camel does not guarantee it can startup
again. The stop is for a hard shutdown. Ideally you should use suspend/resume. Or if in some
app server then restart there, eg where its a full restart of the deployed unit.
> But we could consider keeping custom added components in stop so when you call start
again they are still there.
> For components that has been default created then Camel can create them again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message