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-6023) camel-blueprint - Using blueprint-cm with .cfg files, which triggers bundle reload on .cfg file change, does not startup Camel as expected
Date Wed, 30 Jan 2013 13:25:13 GMT

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

Claus Ibsen resolved CAMEL-6023.
--------------------------------

    Resolution: Fixed
    
> camel-blueprint - Using blueprint-cm with .cfg files, which triggers bundle reload on
.cfg file change, does not startup Camel as expected
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6023
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6023
>             Project: Camel
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 2.10.3
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.10.4, 2.11.0
>
>
> See ARIES-1010
> If you do a restart of a Camel application from the shell
> restart 123
> Then it works fine. But if you change a .cfg file then it wont startup Camel again.
> The workaround is to stop the bundle first, change the .cfg file, and then start the
bundle again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message