[
https://issues.apache.org/activemq/browse/CAMEL-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47708#action_47708
]
William Tam commented on CAMEL-1060:
------------------------------------
Added the logging to DefaultCamelContext since it is probably more reliable
than in LifeCycleStrategy. (A LifeCycleStrategy impl may forget to log the
messages). The version number comes from the manifest so it is available in
unit test.
Modified:
activemq/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java
activemq/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/ServiceSupport.java
activemq/camel/trunk/camel-core/src/main/java/org/apache/camel/util/MainSupport.java
> Camel should log when its started
> ---------------------------------
>
> Key: CAMEL-1060
> URL: https://issues.apache.org/activemq/browse/CAMEL-1060
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.5.0
> Reporter: Claus Ibsen
> Fix For: 2.0.0
>
>
> When using the maven plugins camel:run it logs nicely that Camel has been
> started (with version number).
> {code}
> [pache.camel.spring.Main.main()] MainSupport INFO Apache
> Camel 2.0-SNAPSHOT starting
> {code}
> I think we should add such a feature into camel core itself.
> I think we need two logs
> - starting
> - started
> Such as ActiveMQ does:
> {code}
> BrokerService INFO ActiveMQ 5.1.0 JMS Message Broker
> (localhost) is starting
> BrokerService INFO ActiveMQ JMS Message Broker (localhost,
> ID:claus-acer-1667-1226052031671-0:0) started
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
