[jira] [Commented] (CAMEL-11732) Add or update READMEs to itests

2017-09-05 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11732:


GitHub user tadayosi opened a pull request:

https://github.com/apache/camel/pull/1915

CAMEL-11732: Add or update READMEs to itests

https://issues.apache.org/jira/browse/CAMEL-11732

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tadayosi/camel CAMEL-11732

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1915.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1915


commit b753c17e2eaa8b494c9700374eedb581ebe2ca2d
Author: Tadayoshi Sato 
Date:   2017-09-06T04:31:16Z

CAMEL-11732: Add or update READMEs to itests




> Add or update READMEs to itests
> ---
>
> Key: CAMEL-11732
> URL: https://issues.apache.org/jira/browse/CAMEL-11732
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation, tests
>Affects Versions: 2.19.2
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Minor
>
> There are itests that miss README and some of them are a bit too tricky for 
> newcomers to run as designed, such as {{camel-itest-karaf}} and 
> {{camel-itest-osgi}}.
> It should be better to have READMEs for those itests. Probably adoc format is 
> preferred?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11749) NoTypeConversionAvailableException in wiretap

2017-09-05 Thread Keegan Witt (JIRA) 

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

Keegan Witt updated CAMEL-11749:

Description: 
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=CamelLogger.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}

Changing _SampleCamelRouter_ to
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("bean:camelLogger")
.to("stream:out");
}
}
{code}

Fails with stacktrace
{noformat}
Stacktrace
---

org.apache.camel.NoTypeConversionAvailableException: No type converter 
available to convert from type: null to the required type: java.lang.String 
with value null
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:206)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.SendDynamicProcessor.resolveEndpoint(SendDynamicProcessor.java:144)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:104)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
 [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
 [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158) 
[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153) 
[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
{noformat}

With Camel 2.15.5 or with _SampleCamelRouter_ of content below, exception 
doesn't occur.
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Resource CamelLogger camelLogger;

@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("direct:logging")
.to("stream:out");
from("direct:logging").process(camelLogger);
}
}
{code}

I didn't see anything in release notes in 2.16, 2.17, 2.18, or 2.19 that would 
indicate there's a change in behavior from 2.15 in this regard.  Either this is 
a bug that should be fixed, or the change in behavior should be documented.

  was:
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=CamelLogger.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}

Changing _SampleCamelRouter_ to
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("bean:camelLogger")
.to("stream:out");
}
}
{code}

Fails with stacktrace
{noformat}
Stacktrace

[jira] [Updated] (CAMEL-11749) NoTypeConversionAvailableException in wiretap

2017-09-05 Thread Keegan Witt (JIRA) 

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

Keegan Witt updated CAMEL-11749:

Description: 
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=CamelLogger.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}

Changing _SampleCamelRouter_ to
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("bean:camelLogger")
.to("stream:out");
}
}
{code}

Fails with stacktrace
{noformat}
Stacktrace
---

org.apache.camel.NoTypeConversionAvailableException: No type converter 
available to convert from type: null to the required type: java.lang.String 
with value null
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:206)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.SendDynamicProcessor.resolveEndpoint(SendDynamicProcessor.java:144)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:104)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
 [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
 [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158) 
[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153) 
[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
{noformat}

With Camel 2.15.5 or with _SampleCamelRouter_ of content below, exception 
doesn't occur.
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Resource CamelLogger camelLogger;

@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("direct:logging")
.to("stream:out");
from("direct:logging").process(camelLogger);
}
}
{code}

I didn't see anything in release notes in 2.16, 2.17, 2.18, or 2.19 that would 
indicate there's a change in behavior from 2.15.  Either this is a bug that 
should be fixed, or the change in behavior should be documented.

  was:
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=CamelLogger.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}

Changing _SampleCamelRouter_ to
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("bean:camelLogger")
.to("stream:out");
}
}
{code}

Fails with stacktrace
{noformat}
Stacktrace

[jira] [Updated] (CAMEL-11749) NoTypeConversionAvailableException in wiretap

2017-09-05 Thread Keegan Witt (JIRA) 

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

Keegan Witt updated CAMEL-11749:

Description: 
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=CamelLogger.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}

Changing _SampleCamelRouter_ to
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("bean:camelLogger")
.to("stream:out");
}
}
{code}

Fails with stacktrace
{noformat}
Stacktrace
---

org.apache.camel.NoTypeConversionAvailableException: No type converter 
available to convert from type: null to the required type: java.lang.String 
with value null
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:206)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.SendDynamicProcessor.resolveEndpoint(SendDynamicProcessor.java:144)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:104)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
 ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
 [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
 [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158) 
[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at 
org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153) 
[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
{noformat}

With Camel 2.15.5 or with _SampleCamelRouter_ of content below, exception 
doesn't occur.
{code:java}
@Component
public class SampleCamelRouter extends RouteBuilder {
@Resource CamelLogger camelLogger;

@Override
public void configure() throws Exception {
from("timer:hello?period={{timer.period}}")
.transform(method("myBean", "saySomething"))
.wireTap("direct:logging")
.to("stream:out");
from("direct:logging").process(camelLogger);
}
}
{code}

  was:
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=Bar.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}


> NoTypeConversionAvailableException in wiretap
> -
>
> Key: CAMEL-11749
> URL: https://issues.apache.org/jira/browse/CAMEL-11749
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.19.2
>Reporter: Keegan Witt
>Assignee: Claus Ibsen
>
> # Clone 
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
> # Add _CamelLogger.java_ with contents below to 
> _src/main/java/org/apache/camel/examples_
> {code:title=CamelLogger.java}
> package org.apache.camel.examples;
> import org.apache.camel.Exchange;
> import org.apache.camel.Processor;
>

[jira] [Updated] (CAMEL-11749) NoTypeConversionAvailableException in wiretap

2017-09-05 Thread Keegan Witt (JIRA) 

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

Keegan Witt updated CAMEL-11749:

Affects Version/s: (was: 2.19.1)
   2.19.2

> NoTypeConversionAvailableException in wiretap
> -
>
> Key: CAMEL-11749
> URL: https://issues.apache.org/jira/browse/CAMEL-11749
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.19.2
>Reporter: Keegan Witt
>Assignee: Claus Ibsen
>
> # Clone 
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
> # Add _CamelLogger.java_ with contents below to 
> _src/main/java/org/apache/camel/examples_
> {code:title=CamelLogger.java}
> package org.apache.camel.examples;
> import org.apache.camel.Exchange;
> import org.apache.camel.Processor;
> import org.springframework.stereotype.Component;
> @Component
> public class CamelLogger implements Processor {
> @Override
> public void process(Exchange exchange) {
> System.err.println(exchange.getIn().getBody());
> }
> }
> {code}
> Changing _SampleCamelRouter_ to
> {code:java}
> @Component
> public class SampleCamelRouter extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:hello?period={{timer.period}}")
> .transform(method("myBean", "saySomething"))
> .wireTap("bean:camelLogger")
> .to("stream:out");
> }
> }
> {code}
> Fails with stacktrace
> {noformat}
> Stacktrace
> ---
> org.apache.camel.NoTypeConversionAvailableException: No type converter 
> available to convert from type: null to the required type: java.lang.String 
> with value null
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:206)
>  ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.SendDynamicProcessor.resolveEndpoint(SendDynamicProcessor.java:144)
>  ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:104)
>  ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
>  ~[camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
>  [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
>  [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158) 
> [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153) 
> [camel-core-2.20.0-20170905.112154-218.jar:2.20.0-SNAPSHOT]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_144]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [na:1.8.0_144]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [na:1.8.0_144]
>   at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
> {noformat}
> With Camel 2.15.5 or with _SampleCamelRouter_ of content below, exception 
> doesn't occur.
> {code:java}
> @Component
> public class SampleCamelRouter extends RouteBuilder {
> @Resource CamelLogger camelLogger;
> @Override
> public void configure() throws Exception {
> from("timer:hello?period={{timer.period}}")
> .transform(method("myBean", "saySomething"))
> .wireTap("direct:logging")
> .to("stream:out");
> from("direct:logging").process(camelLogger);
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11749) NoTypeConversionAvailableException in wiretap

2017-09-05 Thread Keegan Witt (JIRA) 

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

Keegan Witt updated CAMEL-11749:

Description: 
# Clone 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
# Add _CamelLogger.java_ with contents below to 
_src/main/java/org/apache/camel/examples_

{code:title=Bar.java}
package org.apache.camel.examples;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.springframework.stereotype.Component;

@Component
public class CamelLogger implements Processor {
@Override
public void process(Exchange exchange) {
System.err.println(exchange.getIn().getBody());
}
}
{code}

  was:
As a workaround to CAMEL-11528, we tried replacing something like 
{code:java}
 from("direct:start")
.wireTap("bean:tap")
.to("mock:result");
{code}
 
with
{code:java}
from("direct:start")
.wiretap("direct:tap")
.to("mock:result");

from("direct:tap")
.process("bean:tapper");
{code}

We got
{noformat}Caused by: org.apache.camel.FailedToCreateRouteException: Failed to 
create route route190 at: >>> process[ref:bean:tapper] <<< in route: 
Route(route190)[[From[direct:tap]] -> [OnException[[clas... because of No bean 
could be found in the registry for: bean:tapper of type: 
org.apache.camel.Processor{noformat}

But if we did
{code:java}
public class MyRoute extends RouteBuilder {
@Resource Tapper tapper;

public void configure() throws Exception {
from("direct:start")
.wiretap("direct:tap")
.to("mock:result");

from("direct:tap")
.process(tapper);
}
}

@Component
public class Tapper implements Processor {
public void Process(Exchange exchange) {}
}
{code}
It worked.


> NoTypeConversionAvailableException in wiretap
> -
>
> Key: CAMEL-11749
> URL: https://issues.apache.org/jira/browse/CAMEL-11749
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.19.1
>Reporter: Keegan Witt
>Assignee: Claus Ibsen
>
> # Clone 
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot
> # Add _CamelLogger.java_ with contents below to 
> _src/main/java/org/apache/camel/examples_
> {code:title=Bar.java}
> package org.apache.camel.examples;
> import org.apache.camel.Exchange;
> import org.apache.camel.Processor;
> import org.springframework.stereotype.Component;
> @Component
> public class CamelLogger implements Processor {
> @Override
> public void process(Exchange exchange) {
> System.err.println(exchange.getIn().getBody());
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11749) NoTypeConversionAvailableException in wiretap

2017-09-05 Thread Keegan Witt (JIRA) 
Keegan Witt created CAMEL-11749:
---

 Summary: NoTypeConversionAvailableException in wiretap
 Key: CAMEL-11749
 URL: https://issues.apache.org/jira/browse/CAMEL-11749
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Affects Versions: 2.19.1
Reporter: Keegan Witt
Assignee: Claus Ibsen


As a workaround to CAMEL-11528, we tried replacing something like 
{code:java}
 from("direct:start")
.wireTap("bean:tap")
.to("mock:result");
{code}
 
with
{code:java}
from("direct:start")
.wiretap("direct:tap")
.to("mock:result");

from("direct:tap")
.process("bean:tapper");
{code}

We got
{noformat}Caused by: org.apache.camel.FailedToCreateRouteException: Failed to 
create route route190 at: >>> process[ref:bean:tapper] <<< in route: 
Route(route190)[[From[direct:tap]] -> [OnException[[clas... because of No bean 
could be found in the registry for: bean:tapper of type: 
org.apache.camel.Processor{noformat}

But if we did
{code:java}
public class MyRoute extends RouteBuilder {
@Resource Tapper tapper;

public void configure() throws Exception {
from("direct:start")
.wiretap("direct:tap")
.to("mock:result");

from("direct:tap")
.process(tapper);
}
}

@Component
public class Tapper implements Processor {
public void Process(Exchange exchange) {}
}
{code}
It worked.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11680) Camel-dropbox should support Put not only from localPath

2017-09-05 Thread Kamil (JIRA) 

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

Kamil commented on CAMEL-11680:
---

why to set CamelFileName since you already specify remotePath?

> Camel-dropbox should support Put not only from localPath
> 
>
> Key: CAMEL-11680
> URL: https://issues.apache.org/jira/browse/CAMEL-11680
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dropbox
>Reporter: Kamil
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> Currently if I want to Put file on Dropbox using Camel-Dopbox I must create 
> temporary file, write to it using file:// and then use: 
> {code}
> dropbox://put?localPath=${header.myTempFile}
> {code}
> which is tedious.
> Camel-dropbox should support writing directly from Exchange



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11184) tests - Add missing tests to itest spring boot

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen reassigned CAMEL-11184:
---

Assignee: Claus Ibsen

> tests - Add missing tests to itest spring boot
> --
>
> Key: CAMEL-11184
> URL: https://issues.apache.org/jira/browse/CAMEL-11184
> Project: Camel
>  Issue Type: Test
>  Components: camel-spring-boot, tests
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> In tests/camel-itest-spring-boot there is a bunch of integration tests of the 
> components running on spring boot.
> But as we have added new components then some are not added here. We should 
> look at the delta and add the missing tests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11184) tests - Add missing tests to itest spring boot

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-11184.
-
Resolution: Fixed

> tests - Add missing tests to itest spring boot
> --
>
> Key: CAMEL-11184
> URL: https://issues.apache.org/jira/browse/CAMEL-11184
> Project: Camel
>  Issue Type: Test
>  Components: camel-spring-boot, tests
>Reporter: Claus Ibsen
> Fix For: 2.20.0
>
>
> In tests/camel-itest-spring-boot there is a bunch of integration tests of the 
> components running on spring boot.
> But as we have added new components then some are not added here. We should 
> look at the delta and add the missing tests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11523) JasyptPropertiesParser fails on properties references with default value

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-11523:
-

Seems like Jasypt is a dying project

> JasyptPropertiesParser fails on properties references with default value
> 
>
> Key: CAMEL-11523
> URL: https://issues.apache.org/jira/browse/CAMEL-11523
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jasypt
>Affects Versions: 2.17.7, 2.19.1
>Reporter: Ronny Aerts
>Priority: Minor
> Attachments: jasypt.rar
>
>
> I'm using the JasyptPropertiesParser in combination with the 
> BridgePropertyPlaceholderConfigurer to able to encrypt properties by adding 
> the parser property.
>  
> 
>  class="org.apache.camel.component.jasypt.JasyptPropertiesParser" 
> depends-on="InitializeProperties">
> value="#{IP.getPassword()}"/>
> value="PBEWITHSHA1ANDRC4_128"/>
> 
>  
> This works fine but when I have a 
> "tris.dlq.folder.process.history:c:/temp/TrisESB" property with a default 
> value in my xml route, the route creating fails with error:
> Caused by: java.lang.IllegalArgumentException: PropertiesComponent with name 
> properties must be defined in CamelContext to support property placeholders. 
> Property with key [tris.dlq.folder.process.history:c:/temp/TrisESB] not found 
> in properties from text: 
> file://{{tris.dlq.folder.process.history:c:/temp/TrisESB}}?fileName=$simple{header.breadcrumbId}-prochist.htm
> My log also mentions the parsing of the property.
> [TRACE] [org.apache.camel.component.jasypt.JasyptPropertiesParser] Parsing 
> property 'tris.dlq.folder.process.history:c:/temp/TrisESB=null'
> It seems that the JasyptPropertiesParser can't handle default properties.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11523) JasyptPropertiesParser fails on properties references with default value

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen updated CAMEL-11523:

Priority: Minor  (was: Major)

> JasyptPropertiesParser fails on properties references with default value
> 
>
> Key: CAMEL-11523
> URL: https://issues.apache.org/jira/browse/CAMEL-11523
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jasypt
>Affects Versions: 2.17.7, 2.19.1
>Reporter: Ronny Aerts
>Priority: Minor
> Attachments: jasypt.rar
>
>
> I'm using the JasyptPropertiesParser in combination with the 
> BridgePropertyPlaceholderConfigurer to able to encrypt properties by adding 
> the parser property.
>  
> 
>  class="org.apache.camel.component.jasypt.JasyptPropertiesParser" 
> depends-on="InitializeProperties">
> value="#{IP.getPassword()}"/>
> value="PBEWITHSHA1ANDRC4_128"/>
> 
>  
> This works fine but when I have a 
> "tris.dlq.folder.process.history:c:/temp/TrisESB" property with a default 
> value in my xml route, the route creating fails with error:
> Caused by: java.lang.IllegalArgumentException: PropertiesComponent with name 
> properties must be defined in CamelContext to support property placeholders. 
> Property with key [tris.dlq.folder.process.history:c:/temp/TrisESB] not found 
> in properties from text: 
> file://{{tris.dlq.folder.process.history:c:/temp/TrisESB}}?fileName=$simple{header.breadcrumbId}-prochist.htm
> My log also mentions the parsing of the property.
> [TRACE] [org.apache.camel.component.jasypt.JasyptPropertiesParser] Parsing 
> property 'tris.dlq.folder.process.history:c:/temp/TrisESB=null'
> It seems that the JasyptPropertiesParser can't handle default properties.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11624) REST DSL/component method Uppercase

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-11624:
-

Can you tell us what component you are using?

> REST DSL/component method Uppercase
> ---
>
> Key: CAMEL-11624
> URL: https://issues.apache.org/jira/browse/CAMEL-11624
> Project: Camel
>  Issue Type: Bug
>  Components: rest
>Affects Versions: 2.19.1
>Reporter: Paolo Lizarazu
> Fix For: 2.20.0, 2.19.3
>
>
> when we are using rest component we need to set the method in uppercase 
> otherwise this will return error 405
> bad example : String requestResponse = 
> testProducer.requestBody("rest:get:health?host=$activityHost:$activityPort", 
> null, String.class)
> working example
> String requestResponse = 
> testProducer.requestBody("rest:GET:health?host=$activityHost:$activityPort", 
> null, String.class)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11664) Split proceeds even if onPrepare throws Exception

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-11664.
-
Resolution: Cannot Reproduce

> Split proceeds even if onPrepare throws Exception
> -
>
> Key: CAMEL-11664
> URL: https://issues.apache.org/jira/browse/CAMEL-11664
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Christoph Läubrich
>Assignee: Claus Ibsen
>
> With the [splitter|http://camel.apache.org/splitter.html] you can set an 
> onPrepareRef to allow custom preprocessing.
> If this processor fails with an exception, the splitting still proceeds 
> leading to hard to track problems becuase the splitter receives messages that 
> are not (or only partially) prepared! Even setting an exception does not let 
> camel fail the split.
> If the prepare step fails camel should fail the split with the exception 
> thrown from onPrepare.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11664) Split proceeds even if onPrepare throws Exception

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-11664:
-

You are using an EOL version of Camel - try with latest. 

The stop on exception works for us, and we see the exception from the on 
prepare failure.
https://github.com/apache/camel/commit/f9cdfeb8753fa7219f66fdf10249e3a1bdf1

> Split proceeds even if onPrepare throws Exception
> -
>
> Key: CAMEL-11664
> URL: https://issues.apache.org/jira/browse/CAMEL-11664
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Christoph Läubrich
>Assignee: Claus Ibsen
>
> With the [splitter|http://camel.apache.org/splitter.html] you can set an 
> onPrepareRef to allow custom preprocessing.
> If this processor fails with an exception, the splitting still proceeds 
> leading to hard to track problems becuase the splitter receives messages that 
> are not (or only partially) prepared! Even setting an exception does not let 
> camel fail the split.
> If the prepare step fails camel should fail the split with the exception 
> thrown from onPrepare.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11680) Camel-dropbox should support Put not only from localPath

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen resolved CAMEL-11680.
-
   Resolution: Fixed
Fix Version/s: 2.20.0

You are welcome to test a SNAPSHOT build if that works for you.

> Camel-dropbox should support Put not only from localPath
> 
>
> Key: CAMEL-11680
> URL: https://issues.apache.org/jira/browse/CAMEL-11680
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dropbox
>Reporter: Kamil
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> Currently if I want to Put file on Dropbox using Camel-Dopbox I must create 
> temporary file, write to it using file:// and then use: 
> {code}
> dropbox://put?localPath=${header.myTempFile}
> {code}
> which is tedious.
> Camel-dropbox should support writing directly from Exchange



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11680) Camel-dropbox should support Put not only from localPath

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen reassigned CAMEL-11680:
---

Assignee: Claus Ibsen

> Camel-dropbox should support Put not only from localPath
> 
>
> Key: CAMEL-11680
> URL: https://issues.apache.org/jira/browse/CAMEL-11680
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dropbox
>Reporter: Kamil
>Assignee: Claus Ibsen
>
> Currently if I want to Put file on Dropbox using Camel-Dopbox I must create 
> temporary file, write to it using file:// and then use: 
> {code}
> dropbox://put?localPath=${header.myTempFile}
> {code}
> which is tedious.
> Camel-dropbox should support writing directly from Exchange



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11680) Camel-dropbox should support Put not only from localPath

2017-09-05 Thread Claus Ibsen (JIRA) 

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

Claus Ibsen commented on CAMEL-11680:
-

You would need to specify a header as well with the name of the file, just like 
the file component has CamelFileName. 

> Camel-dropbox should support Put not only from localPath
> 
>
> Key: CAMEL-11680
> URL: https://issues.apache.org/jira/browse/CAMEL-11680
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dropbox
>Reporter: Kamil
>
> Currently if I want to Put file on Dropbox using Camel-Dopbox I must create 
> temporary file, write to it using file:// and then use: 
> {code}
> dropbox://put?localPath=${header.myTempFile}
> {code}
> which is tedious.
> Camel-dropbox should support writing directly from Exchange



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11729) camel-connector-maven-plugin : generated spring boot starters should support customizers

2017-09-05 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli resolved CAMEL-11729.
-
Resolution: Fixed

> camel-connector-maven-plugin : generated spring boot starters should support 
> customizers 
> -
>
> Key: CAMEL-11729
> URL: https://issues.apache.org/jira/browse/CAMEL-11729
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-connector, tooling
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11730) camel-connector-maven-plugin : it should be possible to configure connector only properties

2017-09-05 Thread Luca Burgazzoli (JIRA) 

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

Luca Burgazzoli resolved CAMEL-11730.
-
Resolution: Fixed

> camel-connector-maven-plugin : it should be possible to configure connector 
> only properties
> ---
>
> Key: CAMEL-11730
> URL: https://issues.apache.org/jira/browse/CAMEL-11730
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-connector, tooling
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> the connector json may have something like: 
> {code}
> "connectorProperties": {
> "myProp": { "kind": "property", "displayName": "xyz", ... }
> },
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11680) Camel-dropbox should support Put not only from localPath

2017-09-05 Thread Kamil (JIRA) 

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

Kamil commented on CAMEL-11680:
---

Supporting just byte[] in @Body should be enough for the MVP

> Camel-dropbox should support Put not only from localPath
> 
>
> Key: CAMEL-11680
> URL: https://issues.apache.org/jira/browse/CAMEL-11680
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-dropbox
>Reporter: Kamil
>
> Currently if I want to Put file on Dropbox using Camel-Dopbox I must create 
> temporary file, write to it using file:// and then use: 
> {code}
> dropbox://put?localPath=${header.myTempFile}
> {code}
> which is tedious.
> Camel-dropbox should support writing directly from Exchange



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11715) Camel Spring : unable to mix xml and java routes

2017-09-05 Thread Zoran Regvart (JIRA) 

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

Zoran Regvart commented on CAMEL-11715:
---

I've pushed a fix for this [~lb] would you mind verifying it works with your 
example? Thanks (y)

> Camel Spring : unable to mix xml and java routes
> 
>
> Key: CAMEL-11715
> URL: https://issues.apache.org/jira/browse/CAMEL-11715
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring, camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.20.0
>
>
> I camel 2.19 it was possible to mix routes from Spring XML and Spring boot 
> but that does not work anymore with camel 2.20.x.
> A sample project can be found here: 
> https://github.com/lburgazzoli/camel-spring-xml so if you switch camel 
> version, you'd see that the java route is not more loaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11748) Camel-Undertow: transferException option doesn't work

2017-09-05 Thread Andrea Cosentino (JIRA) 
Andrea Cosentino created CAMEL-11748:


 Summary: Camel-Undertow: transferException option doesn't work
 Key: CAMEL-11748
 URL: https://issues.apache.org/jira/browse/CAMEL-11748
 Project: Camel
  Issue Type: Bug
  Components: camel-undertow
Affects Versions: 2.19.2
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Priority: Minor
 Fix For: 2.18.5, 2.20.0, 2.19.3






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11430) Add support for Spring Boot 2.0.x

2017-09-05 Thread Marcin Grzejszczak (JIRA) 

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

Marcin Grzejszczak commented on CAMEL-11430:


Ok, so please comment on this issue once you have this resolved. Until then 
I'll drop the support of Apache Camel in 2.0.x Boot based versions of Spring 
Cloud Contract

> Add support for Spring Boot 2.0.x
> -
>
> Key: CAMEL-11430
> URL: https://issues.apache.org/jira/browse/CAMEL-11430
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Marcin Grzejszczak
> Fix For: Future
>
>
> Hello!
> It would be great to add compatibility with Boot 2.0.x . Spring Cloud 
> Contract uses Camel but in the 2.0.x branch (that is compatible with Boot 
> 2.0.x ) we can't actually use it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11733) camel-google-bigquery : Incorrectly set partition name

2017-09-05 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CAMEL-11733:


Github user asfgit closed the pull request at:

https://github.com/apache/camel/pull/1914


> camel-google-bigquery : Incorrectly set partition name
> --
>
> Key: CAMEL-11733
> URL: https://issues.apache.org/jira/browse/CAMEL-11733
> Project: Camel
>  Issue Type: Bug
>Reporter: Evgeny Minkevich
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> When Partition Decorator is set as:
> {code:java}
> .setHeader(GoogleBigQueryConstants.PARTITION_DECORATOR,simple("20170901"))
> {code}
> The exception is thrown:
> {code}
> Invalid table ID \\\"table_name?20170901
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11715) Camel Spring : unable to mix xml and java routes

2017-09-05 Thread Zoran Regvart (JIRA) 

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

Zoran Regvart commented on CAMEL-11715:
---

I think I found the issue, again, it's simple ordering of RoutesCollector, 
CamelContextFactoryBean and SpringCamelContext. Running all tests to confirm.

> Camel Spring : unable to mix xml and java routes
> 
>
> Key: CAMEL-11715
> URL: https://issues.apache.org/jira/browse/CAMEL-11715
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring, camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.20.0
>
>
> I camel 2.19 it was possible to mix routes from Spring XML and Spring boot 
> but that does not work anymore with camel 2.20.x.
> A sample project can be found here: 
> https://github.com/lburgazzoli/camel-spring-xml so if you switch camel 
> version, you'd see that the java route is not more loaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11715) Camel Spring : unable to mix xml and java routes

2017-09-05 Thread Zoran Regvart (JIRA) 

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

Zoran Regvart commented on CAMEL-11715:
---

The fix I have causes deadlock (probably route not started) in 
{{camel-spring-cloud}} 
(_org.apache.camel.spring.cloud.CamelSpringCloudServiceCallRibbonTest_) test. I 
need to investigate that case. It's quite common to make a change in one part 
of our Spring support and cause an issue in another :(

> Camel Spring : unable to mix xml and java routes
> 
>
> Key: CAMEL-11715
> URL: https://issues.apache.org/jira/browse/CAMEL-11715
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring, camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
> Fix For: 2.20.0
>
>
> I camel 2.19 it was possible to mix routes from Spring XML and Spring boot 
> but that does not work anymore with camel 2.20.x.
> A sample project can be found here: 
> https://github.com/lburgazzoli/camel-spring-xml so if you switch camel 
> version, you'd see that the java route is not more loaded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)