[jira] Created: (CAMEL-965) When camel-osgi is on the classpath but camel is not used in an OSGi context, camel-osgi behaves badly

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-965) When camel-osgi is on the classpath but camel is not used in an OSGi context, camel-osgi behaves badly

JIRA jira@apache.org
When camel-osgi is on the classpath but camel is not used in an OSGi context, camel-osgi behaves badly
------------------------------------------------------------------------------------------------------

                 Key: CAMEL-965
                 URL: https://issues.apache.org/activemq/browse/CAMEL-965
             Project: Apache Camel
          Issue Type: Bug
            Reporter: Guillaume Nodet
            Assignee: Guillaume Nodet
             Fix For: 1.5.0




--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-965) When camel-osgi is on the classpath but camel is not used in an OSGi context, camel-osgi behaves badly

JIRA jira@apache.org

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

Guillaume Nodet resolved CAMEL-965.
-----------------------------------

    Resolution: Fixed

Sending        components/camel-osgi/src/main/java/org/apache/camel/osgi/CamelContextFactoryBean.java
Transmitting file data .
Committed revision 702569.

> When camel-osgi is on the classpath but camel is not used in an OSGi context, camel-osgi behaves badly
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-965
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-965
>             Project: Apache Camel
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: 1.5.0
>
>


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.