[jira] [Updated] (CAMEL-18791) MDC logging not work after JMS Consumer

2022-12-02 Thread Alexander Domke (Jira)


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

Alexander Domke updated CAMEL-18791:

Description: 
The MDC logging in connection with the JMS component does not work properly. 
Although MDC logging is switched on in the CamelContext and MDC logging has 
been configured, the log file is not filled. During further tests I found out 
that logging only works if the first JMS message is sent from the same 
CamelContext.  Unfortunately, it is out of the question for us to change the 
JMS component to synchronous operation.  I hope my hint helps you to fix the 
component.

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0;
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
           xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
                               http://camel.apache.org/schema/blueprint 
http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
    
        
        
        
        
        
        
        
    
        http://camel.apache.org/schema/blueprint;>        

        
            
            
                my message
            
            
        
        
        
                        
            
        
    
 {code}
 
 
 

 

  was:
The MDC logging in connection with the JMS component does not work properly. 
Although MDC logging is switched on in the CamelContext and MDC logging has 
been configured, the log file is not filled. During further tests I found out 
that logging only works if the first JMS message is sent from the same 
CamelContext.  Unfortunately, it is out of the question for us to change the 
JMS component to synchronous operation.  I hope my hint helps you to fix the 
component.

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0;
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
           xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
                               http://camel.apache.org/schema/blueprint 
http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
    
        
        
        
        
        
        
        
    
        http://camel.apache.org/schema/blueprint;>        

        
            
            
                my message
            
            
        
        
        
                        
            
        
    
 {code}
 
 
 

 


> MDC logging not work after JMS Consumer
> ---
>
> Key: CAMEL-18791
> URL: https://issues.apache.org/jira/browse/CAMEL-18791
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jms
>Affects Versions: 3.18.3
>Reporter: Alexander Domke
>Priority: Major
>
> The MDC logging in connection with the JMS component does not work properly. 
> Although MDC logging is switched on in the CamelContext and MDC logging has 
> been configured, the log file is not filled. During further tests I found out 
> that logging only works if the first JMS message is sent from the same 
> CamelContext.  Unfortunately, it is out of the question for us to change the 
> JMS component to synchronous operation.  I hope my hint helps you to fix the 
> component.
> *blueprint.xml*
> {code:java}
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>            xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>                                http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
>  filter="(osgi.jndi.service.name=artemis)" />     class="org.springframework.jms.connection.JmsTransactionManager">
>         
>          class="org.apache.camel.spring.spi.SpringTransactionPolicy">
>         
>          class="org.apache.camel.component.jms.JmsComponent">
>         
>         
>         
>     
>          autoStartup="true" xmlns="http://camel.apache.org/schema/blueprint;>        
> 
>         
>             
>             
>                 my message
>             
>             
>         
>         
>         
>                         
>             
>         
>     
>  {code}
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (CAMEL-18791) MDC logging not work after JMS Consumer

2022-12-02 Thread Alexander Domke (Jira)


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

Alexander Domke updated CAMEL-18791:

Description: 
The MDC logging in connection with the JMS component does not work properly. 
Although MDC logging is switched on in the CamelContext and MDC logging has 
been configured, the log file is not filled. During further tests I found out 
that logging only works if the first JMS message is sent from the same 
CamelContext.  Unfortunately, it is out of the question for us to change the 
JMS component to synchronous operation.  I hope my hint helps you to fix the 
component.

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0;
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
           xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
                               http://camel.apache.org/schema/blueprint 
http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
    
        
        
        
        
        
        
        
    
        http://camel.apache.org/schema/blueprint;>        

        
            
            
                my message
            
            
        
        
        
                        
            
        
    
 {code}
 
 
 

 

  was:
The MDC logging in connection with the JMS component does not work properly. 
Although MDC logging is switched on in the CamelContext and MDC logging has 
been configured, the log file is not filled. During further tests I found out 
that logging only works if the first JMS message is sent from the same 
CamelContext.  Unfortunately, it is out of the question for us to change the 
JMS component to synchronous operation.  I hope my hint helps you to fix the 
component.

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0;
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
           xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
                               http://camel.apache.org/schema/blueprint 
http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
    
        
        
        
        
        
        
        
    
        http://camel.apache.org/schema/blueprint;>        

        
            
            
                my message
            
            
        
        
        
                        
            
        
    
 {code}


> MDC logging not work after JMS Consumer
> ---
>
> Key: CAMEL-18791
> URL: https://issues.apache.org/jira/browse/CAMEL-18791
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jms
>Affects Versions: 3.18.3
>Reporter: Alexander Domke
>Priority: Major
>
> The MDC logging in connection with the JMS component does not work properly. 
> Although MDC logging is switched on in the CamelContext and MDC logging has 
> been configured, the log file is not filled. During further tests I found out 
> that logging only works if the first JMS message is sent from the same 
> CamelContext.  Unfortunately, it is out of the question for us to change the 
> JMS component to synchronous operation.  I hope my hint helps you to fix the 
> component.
> *blueprint.xml*
> {code:java}
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>            xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
>                                http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
>  filter="(osgi.jndi.service.name=artemis)" />     class="org.springframework.jms.connection.JmsTransactionManager">
>         
>          class="org.apache.camel.spring.spi.SpringTransactionPolicy">
>         
>          class="org.apache.camel.component.jms.JmsComponent">
>         
>         
>         
>     
>          autoStartup="true" xmlns="http://camel.apache.org/schema/blueprint;>        
> 
>         
>             
>             
>                 my message
>             
>             
>         
>         
>         
>                         
>             
>         
>     
>  {code}
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CAMEL-18791) MDC logging not work after JMS Consumer

2022-12-02 Thread Alexander Domke (Jira)
Alexander Domke created CAMEL-18791:
---

 Summary: MDC logging not work after JMS Consumer
 Key: CAMEL-18791
 URL: https://issues.apache.org/jira/browse/CAMEL-18791
 Project: Camel
  Issue Type: Bug
  Components: camel-jms
Affects Versions: 3.18.3
Reporter: Alexander Domke


The MDC logging in connection with the JMS component does not work properly. 
Although MDC logging is switched on in the CamelContext and MDC logging has 
been configured, the log file is not filled. During further tests I found out 
that logging only works if the first JMS message is sent from the same 
CamelContext.  Unfortunately, it is out of the question for us to change the 
JMS component to synchronous operation.  I hope my hint helps you to fix the 
component.

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0;
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
           xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
                               http://camel.apache.org/schema/blueprint 
http://camel.apache.org/schema/blueprint/camel-blueprint-3.18.2.xsd;>    
    
        
        
        
        
        
        
        
    
        http://camel.apache.org/schema/blueprint;>        

        
            
            
                my message
            
            
        
        
        
                        
            
        
    
 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (CAMEL-18598) Camel Context starts automatically even if autoStartup="false"

2022-10-11 Thread Alexander Domke (Jira)


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

Alexander Domke updated CAMEL-18598:

Description: 
I have a simple blueprint.xml with a Camel Context and option 
autoStartup="false".

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>

http://camel.apache.org/schema/blueprint; id="test" 
autoStartup="false">







{code}
What puzzles me is that the CamelContext starts automatically although 
according to the configuration it should not. Is there a possibility to 
influence the behavior?

*I use:* karaf 4.4.1, camel 3.18.2
 
 
 

 

  was:
I have a simple blueprint.xml with a Camel Context and option 
autoStartup="false". 

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>

http://camel.apache.org/schema/blueprint; id="test" 
autoStartup="false">







{code}

What puzzles me is that the CamelContext starts automatically although 
according to the configuration it should not. Is there a possibility to 
influence the behavior?

*I use:* karaf 4.4.1, camel 3.18.2



> Camel Context starts automatically even if autoStartup="false"
> --
>
> Key: CAMEL-18598
> URL: https://issues.apache.org/jira/browse/CAMEL-18598
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, camel-core
>Affects Versions: 3.18.2
>Reporter: Alexander Domke
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I have a simple blueprint.xml with a Camel Context and option 
> autoStartup="false".
> *blueprint.xml*
> {code:java}
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> http://camel.apache.org/schema/blueprint; id="test" 
> autoStartup="false">
> 
> 
> 
>   
> 
> 
> {code}
> What puzzles me is that the CamelContext starts automatically although 
> according to the configuration it should not. Is there a possibility to 
> influence the behavior?
> *I use:* karaf 4.4.1, camel 3.18.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CAMEL-18598) Camel Context starts automatically even if autoStartup="false"

2022-10-10 Thread Alexander Domke (Jira)
Alexander Domke created CAMEL-18598:
---

 Summary: Camel Context starts automatically even if 
autoStartup="false"
 Key: CAMEL-18598
 URL: https://issues.apache.org/jira/browse/CAMEL-18598
 Project: Camel
  Issue Type: Bug
  Components: camel-blueprint, camel-core
Affects Versions: 3.18.2
Reporter: Alexander Domke
Assignee: Grzegorz Grzybek


I have a simple blueprint.xml with a Camel Context and option 
autoStartup="false". 

*blueprint.xml*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>

http://camel.apache.org/schema/blueprint; id="test" 
autoStartup="false">







{code}

What puzzles me is that the CamelContext starts automatically although 
according to the configuration it should not. Is there a possibility to 
influence the behavior?

*I use:* karaf 4.4.1, camel 3.18.2




--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CAMEL-18545) Load a route from XML file does not work

2022-09-25 Thread Alexander Domke (Jira)


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

Alexander Domke commented on CAMEL-18545:
-

Hi Claus, thanks for your quick reply. Also my attempt to extend a Blueprint 
Camel Context at runtime with additional routes was not successful. Here is the 
approach:

*My Test Implementation:*
{code:java}
package testbundle;

import java.io.File;
import java.nio.file.Files;

import org.apache.camel.CamelContext;
import org.apache.camel.Exchange;
import org.apache.camel.ExtendedCamelContext;
import org.apache.camel.ProducerTemplate;
import org.apache.camel.blueprint.BlueprintCamelContext;
import org.apache.camel.spi.Resource;
import org.apache.camel.support.DefaultExchange;
import org.apache.camel.support.ResourceHelper;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.Reference;

@Component(
immediate = true,
service = TestBundle.class,
property = {"osgi.command.scope=test", "osgi.command.function=loadRoutes"})
public class TestBundle {

  public BlueprintCamelContext camelContext;

  @Reference(target = "(camel.context.name=dummyCamelContext)")
  public void bindCamelContext(CamelContext camelContext) {
this.camelContext = (BlueprintCamelContext) camelContext;
  }

  public void unbindCamelContext() {
camelContext = null;
  }

  public void loadRoutes() throws Exception {
loadRoute("C:\\tmp\\before_create.xml", camelContext);
camelContext.start();
Exchange exchange = new DefaultExchange(camelContext);
ProducerTemplate producerTemplate = 
exchange.getContext().createProducerTemplate();
Exchange resultExchange = producerTemplate.send("direct:start", exchange);
System.out.println("resultExchange: " + resultExchange);

if (resultExchange.getException() != null) {
  throw resultExchange.getException();
}
  }

  private void loadRoute(String name, BlueprintCamelContext camelContext) {
ExtendedCamelContext ecc = camelContext.adapt(ExtendedCamelContext.class);
try {
  File file = new File(name);
  byte[] content = Files.readAllBytes(file.toPath());
  Resource resource = ResourceHelper.fromBytes(file.getAbsolutePath(), 
content);
  ecc.getRoutesLoader().loadRoutes(resource);
  System.out.println("ecc routes: " + ecc.getRoutes());
  System.out.println("camelContext routes: " + 
camelContext.getRouteDefinitions());

} catch (Exception e) {
  throw new RuntimeException(e);
}
  }
}

{code}

*My Blueprint with camel context:*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0; 
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0; 
xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0; xsi:schemaLocation="
   http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint; 
id="dummyCamelContext">






{code}


*My Route to load:*
{code:java}

http://www.osgi.org/xmlns/blueprint/v1.0.0;>
http://www.w3.org/2001/XMLSchema-instance; 
xmlns="http://camel.apache.org/schema/blueprint; xsi:schemaLocation="
http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;>







{code}

Error executing command: No consumers available on endpoint: direct://start. 
Exchange[]

I am at a loss, do you have any idea what I am doing wrong?


> Load a route from XML file does not work
> 
>
> Key: CAMEL-18545
> URL: https://issues.apache.org/jira/browse/CAMEL-18545
> Project: Camel
>  Issue Type: Bug
>  Components: camel-blueprint, camel-osgi
>Reporter: Alexander Domke
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> Hello together!
> I am trying to load an XML route in a Karaf OSGi runtime and add it to a 
> camel context. Then I plan to pass an exchange to the endpoint from the 
> loaded route. All my attempts so far have failed and I don't know what to do 
> anymore. I have already investigated open Camel Jira issues and found nothing 
> that points to an existing problem. 
> *My Test Implementation:*
> {code:java}
> package testbundle;
> import java.io.File;
> import java.nio.file.Files;
> import org.apache.camel.Exchange;
> import org.apache.camel.ProducerTemplate;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.core.osgi.OsgiCamelContextHelper;
> import org.apache.camel.core.osgi.OsgiCamelContextPublisher;
> import org.apache.camel.core.osgi.OsgiDefaultCamelContext;
> import 

[jira] [Created] (CAMEL-18545) Load a route from XML file does not work

2022-09-23 Thread Alexander Domke (Jira)
Alexander Domke created CAMEL-18545:
---

 Summary: Load a route from XML file does not work
 Key: CAMEL-18545
 URL: https://issues.apache.org/jira/browse/CAMEL-18545
 Project: Camel
  Issue Type: Bug
  Components: camel-blueprint, camel-osgi
Reporter: Alexander Domke
Assignee: Grzegorz Grzybek


Hello together!

I am trying to load an XML route in a Karaf OSGi runtime and add it to a camel 
context. Then I plan to pass an exchange to the endpoint from the loaded route. 
All my attempts so far have failed and I don't know what to do anymore. I have 
already investigated open Camel Jira issues and found nothing that points to an 
existing problem. 

*My Test Implementation:*

{code:java}
package testbundle;

import java.io.File;
import java.nio.file.Files;

import org.apache.camel.Exchange;
import org.apache.camel.ProducerTemplate;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.core.osgi.OsgiCamelContextHelper;
import org.apache.camel.core.osgi.OsgiCamelContextPublisher;
import org.apache.camel.core.osgi.OsgiDefaultCamelContext;
import org.apache.camel.dsl.xml.io.XmlRoutesBuilderLoader;
import org.apache.camel.impl.DefaultCamelContext;
import org.apache.camel.spi.Resource;
import org.apache.camel.support.DefaultExchange;
import org.apache.camel.support.ResourceHelper;
import org.osgi.framework.BundleContext;
import org.osgi.service.component.annotations.Activate;
import org.osgi.service.component.annotations.Component;

@Component(
immediate = true,
service = TestBundle.class,
property = {"osgi.command.scope=test", "osgi.command.function=loadRoutes"})
public class TestBundle {

  private BundleContext bundleContext;

  @Activate
  public void activate(BundleContext bundleContext) {
this.bundleContext = bundleContext;
  }

  public void loadRoutes() throws Exception {
OsgiDefaultCamelContext camelContext = null;
try (OsgiCamelContextPublisher publisher = new 
OsgiCamelContextPublisher(bundleContext); ) {
  camelContext = new OsgiDefaultCamelContext(bundleContext);
  OsgiCamelContextHelper.osgiUpdate(camelContext, bundleContext);
  publisher.registerCamelContext(camelContext);

  loadRoute("C:\\tmp\\before_create.xml", (DefaultCamelContext) 
camelContext);

  camelContext.start();

  Exchange exchange = new DefaultExchange(camelContext);
  ProducerTemplate producerTemplate = 
exchange.getContext().createProducerTemplate();
  Exchange resultExchange = producerTemplate.send("direct:start", exchange);
  System.out.println("resultExchange: " + resultExchange);

  if (resultExchange.getException() != null) {
throw resultExchange.getException();
  }
} finally {
  camelContext.stop();
}
  }

  private void loadRoute(String name, DefaultCamelContext camelContext) {
try {
  File file = new File(name);
  byte[] content = Files.readAllBytes(file.toPath());

  Resource resource = ResourceHelper.fromBytes(file.getAbsolutePath(), 
content);
  RouteBuilder builder =
  (RouteBuilder) new 
XmlRoutesBuilderLoader().loadRoutesBuilder(resource);
  builder.setCamelContext(camelContext);
  builder.configure();

} catch (Exception e) {
  throw new RuntimeException(e);
}
  }
}
{code}

*My Test Route:*
{code:xml}
http://www.w3.org/2001/XMLSchema-instance;
xmlns="http://camel.apache.org/schema/spring;
xsi:schemaLocation="
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;>






{code}


*Installed Karaf Features:*

{code:java}
Name| Version | Required | State   | Repository | Description
+-+--+-++--
xml-specs-api   | 2.9.0   |  | Started | camel-3.18.2   |
camel   | 3.18.2  | x| Started | camel-3.18.2   |
camel-core  | 3.18.2  |  | Started | camel-3.18.2   |
camel-blueprint | 3.18.2  | x| Started | camel-3.18.2   |
camel-jaxb  | 3.18.2  | x| Started | camel-3.18.2   |
aries-proxy | 4.4.1   |  | Started | standard-4.4.1 | Aries Proxy
aries-blueprint | 4.4.1   |  | Started | standard-4.4.1 | Aries 
Blueprint
feature | 4.4.1   | x| Started | standard-4.4.1 | Features 
Support
shell   | 4.4.1   | x| Started | standard-4.4.1 | Karaf Shell
deployer| 4.4.1   | x| Started | standard-4.4.1 | Karaf Deployer
bundle  | 4.4.1   | x| Started | standard-4.4.1 | Provide 
Bundle support
config  | 4.4.1   | x| Started | standard-4.4.1 | Provide OSGi 
ConfigAdmin support
diagnostic  | 4.4.1   | x| Started | standard-4.4.1 | Provide 
Diagnostic support
instance| 4.4.1   | 

[jira] [Commented] (CAMEL-14614) org.apache.camel.model.config doesnt contain ObjectFactory.class

2020-02-25 Thread Alexander Domke (Jira)


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

Alexander Domke commented on CAMEL-14614:
-

[~davsclaus]Hello Claus, we have been using Apache Karaf, Apache Camel and 
Spring Frameworks for many years. So far we have successfully mastered all 
problems related to spring integration. I will see if I can still solve it this 
time if a lot of services don't have to be migrated. 
Is it still that aries blueprint does not support imports?
greeting
Alex

> org.apache.camel.model.config doesnt contain ObjectFactory.class
> 
>
> Key: CAMEL-14614
> URL: https://issues.apache.org/jira/browse/CAMEL-14614
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Alexander Domke
>Priority: Major
>
> Hello everybody,
> I have problems with the Camel update to version 3.0.1.
> We currently use Apache Karaf 4.2.7 + Spring Deployer + Gemini Blueprint 3.0 
> + Camel 2.23.2.
> After updating from Camel 2.23.2 to 3.0.1 I get unexpected errors:
> {code:java}
> 11:14:35.440 ERROR [EclipseGeminiBlueprintExtenderThread-1] Unable to create 
> application context for [camel-context.xml], unsatisfied dependencies: none
> org.springframework.beans.factory.BeanDefinitionStoreException: Failed to 
> create the JAXB binder; nested exception is javax.xml.bind.JAXBException: 
> "org.apache.camel.model.config" doesnt contain ObjectFactory.class or 
> jaxb.index
> at 
> org.apache.camel.spring.handler.CamelNamespaceHandler$CamelContextBeanDefinitionParser.doParse(CamelNamespaceHandler.java:349)
>  ~[?:?]
> at 
> org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:88)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:63)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:74)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1391)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1371)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:179)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:513)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:393)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:224)
>  ~[!/:?]
> at 
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:195)
>  ~[!/:?]
> at 
> org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:171)
>  ~[?:?]
> at 
> org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:141)
>  ~[?:?]
> at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:133)
>  ~[!/:?]
> at 
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:636)
>  ~[!/:?]
> at 
> org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$800(AbstractDelegatedExecutionApplicationContext.java:57)
>  ~[!/:3.0.0.M01]
> at 
> 

[jira] [Created] (CAMEL-14614) org.apache.camel.model.config doesnt contain ObjectFactory.class

2020-02-25 Thread Alexander Domke (Jira)
Alexander Domke created CAMEL-14614:
---

 Summary: org.apache.camel.model.config doesnt contain 
ObjectFactory.class
 Key: CAMEL-14614
 URL: https://issues.apache.org/jira/browse/CAMEL-14614
 Project: Camel
  Issue Type: Bug
Affects Versions: 3.0.1
Reporter: Alexander Domke


Hello everybody,

I have problems with the Camel update to version 3.0.1.

We currently use Apache Karaf 4.2.7 + Spring Deployer + Gemini Blueprint 3.0 + 
Camel 2.23.2.
After updating from Camel 2.23.2 to 3.0.1 I get unexpected errors:


{code:java}
11:14:35.440 ERROR [EclipseGeminiBlueprintExtenderThread-1] Unable to create 
application context for [camel-context.xml], unsatisfied dependencies: none
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to 
create the JAXB binder; nested exception is javax.xml.bind.JAXBException: 
"org.apache.camel.model.config" doesnt contain ObjectFactory.class or jaxb.index
at 
org.apache.camel.spring.handler.CamelNamespaceHandler$CamelContextBeanDefinitionParser.doParse(CamelNamespaceHandler.java:349)
 ~[?:?]
at 
org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:88)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:63)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:74)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1391)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1371)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:179)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:513)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:393)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
 ~[!/:?]
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
 ~[!/:?]
at 
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188)
 ~[!/:?]
at 
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:224)
 ~[!/:?]
at 
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:195)
 ~[!/:?]
at 
org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:171)
 ~[?:?]
at 
org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:141)
 ~[?:?]
at 
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:133)
 ~[!/:?]
at 
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:636)
 ~[!/:?]
at 
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$800(AbstractDelegatedExecutionApplicationContext.java:57)
 ~[!/:3.0.0.M01]
at 
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$3.run(AbstractDelegatedExecutionApplicationContext.java:239)
 ~[!/:3.0.0.M01]
at 
org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
 ~[!/:3.0.0.M01]
at 
org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.startRefresh(AbstractDelegatedExecutionApplicationContext.java:217)
 ~[!/:3.0.0.M01]
at 
org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:224)
 [!/:?]
at