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

Raul Kripalani commented on CAMEL-5010:
---------------------------------------

Actually, it needs to be reverted entirely. 

Claus, I believe the code is not simply doing logging, it is actually 
overriding the CamelContextFactoryBean being used. It starts off by statically 
using the Spring one, and if the OSGi one is available, it switches to that one.
                
> Renove OSGi environment detection logging from camel-spring
> -----------------------------------------------------------
>
>                 Key: CAMEL-5010
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5010
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.1, 2.10.0
>
>
> In the old days when using OSGi and Camel it was sometime tricky to get the 
> stuff working and running correctly. So we had some logic to detect if OSGi 
> environment. We have some left over code in camel-spring that logs this. We 
> should now remove this as it does not offer any value.
> And also causes a WARN to be logged in JBoss7 that may confuse users, when 
> using Camel as a WAR app in JBoss.
> http://camel.465427.n5.nabble.com/Camel-2-9-0-startup-error-message-ClassNotFoundException-org-osgi-framework-BundleActivator-tp5133932p5133932.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to