[jira] [Resolved] (CAMEL-9687) camel-swagger - Should use resolved placeholders in output

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9687.

Resolution: Fixed

> camel-swagger - Should use resolved placeholders in output
> --
>
> Key: CAMEL-9687
> URL: https://issues.apache.org/jira/browse/CAMEL-9687
> Project: Camel
>  Issue Type: Bug
>  Components: camel-swagger
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/camel-swagger-java-not-parse-property-tp5778734.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9682) camel-rxjava module should extend Bean Binding to support methods returning Observable

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9682:
---
Component/s: camel-rx

> camel-rxjava module should extend Bean Binding to support methods returning 
> Observable
> -
>
> Key: CAMEL-9682
> URL: https://issues.apache.org/jira/browse/CAMEL-9682
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-rx
>Reporter: james strachan
>
> when making asynchronous InOut requests it'd be nice if methods could return 
> Observable so that we could use the RxJava async programming model to 
> process async requests & responses.
> e.g. kinda like how folks can use Retrofit for HTTP: 
> http://joluet.github.io/blog/2014/07/07/rxjava-retrofit/
> {code}
> public interface MyThing {
> @GET("/session.json")
> Observable login();
> @GET("/user.json")
> Observable getUserState();
> }
> {code}
> to then let you use the normal composition / join / flatMap stuff in RxJava 
> to compose multiple requests across different microservice invocations 
> together with timeouts etc e.g. to compose the latest from 2 calls:
> {code}
> Observable.combineLatest(api.fetchUserProfile(), api.getUserState(),
> (user, userStatus) -> new Pair<>(user, userStatus));
> {code}
> Where we'd replace the @GET annotation with a bean binding annotation and a 
> URI parameter to switch to using ActiveMQ or Twitter or whatever



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9688) Documentation: Wrong header name on smpp wiki page

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9688.

   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.17.0

> Documentation: Wrong header name on smpp wiki page
> --
>
> Key: CAMEL-9688
> URL: https://issues.apache.org/jira/browse/CAMEL-9688
> Project: Camel
>  Issue Type: Task
>  Components: camel-smpp, documentation
>Affects Versions: 2.16.2
>Reporter: Pascal Schumacher
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.0
>
>
> There is a small error on the http://camel.apache.org/smpp.html wiki page. At 
> least in 2.16.2 and current master there is no header called 
> "CamelSmppFinalStatus", the header is called "CamelSmppStatus" (see: 
> https://github.com/apache/camel/blob/cc9924f41965885af25027fc053adaf21f15b5b4/components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConstants.java#L41)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9688) Documentation: Wrong header name on smpp wiki page

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9688:
---
Issue Type: Task  (was: Bug)

> Documentation: Wrong header name on smpp wiki page
> --
>
> Key: CAMEL-9688
> URL: https://issues.apache.org/jira/browse/CAMEL-9688
> Project: Camel
>  Issue Type: Task
>  Components: camel-smpp, documentation
>Affects Versions: 2.16.2
>Reporter: Pascal Schumacher
>Priority: Minor
>
> There is a small error on the http://camel.apache.org/smpp.html wiki page. At 
> least in 2.16.2 and current master there is no header called 
> "CamelSmppFinalStatus", the header is called "CamelSmppStatus" (see: 
> https://github.com/apache/camel/blob/cc9924f41965885af25027fc053adaf21f15b5b4/components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConstants.java#L41)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9689) Websocket Component Failing to Install in Karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9689:
---
Priority: Major  (was: Critical)

> Websocket Component Failing to Install in Karaf
> ---
>
> Key: CAMEL-9689
> URL: https://issues.apache.org/jira/browse/CAMEL-9689
> Project: Camel
>  Issue Type: Bug
>  Components: camel-websocket, karaf
>Affects Versions: 2.16.2
> Environment: Oracle Java 8, Apache Karaf 4.0.4
>Reporter: Trey Sargent
>
> When installing the camel-websocket component in Karaf 4.0.4 the process 
> fails with the following message:
> Error executing command: Unable to resolve javax.mail/1.4.5: missing 
> requirement [javax.mail/1.4.5] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=com.sun.mail.handlers)(version>=1.4.0))"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9689) Websocket Component Failing to Install in Karaf

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9689:
---
Component/s: karaf

> Websocket Component Failing to Install in Karaf
> ---
>
> Key: CAMEL-9689
> URL: https://issues.apache.org/jira/browse/CAMEL-9689
> Project: Camel
>  Issue Type: Bug
>  Components: camel-websocket, karaf
>Affects Versions: 2.16.2
> Environment: Oracle Java 8, Apache Karaf 4.0.4
>Reporter: Trey Sargent
>
> When installing the camel-websocket component in Karaf 4.0.4 the process 
> fails with the following message:
> Error executing command: Unable to resolve javax.mail/1.4.5: missing 
> requirement [javax.mail/1.4.5] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=com.sun.mail.handlers)(version>=1.4.0))"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9690) bean parameter binding should check parameter types

[Minh Tran (JIRA)]

Minh Tran created CAMEL-9690:


 Summary: bean parameter binding should check parameter types
 Key: CAMEL-9690
 URL: https://issues.apache.org/jira/browse/CAMEL-9690
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Affects Versions: 2.16.2
 Environment: mac
Reporter: Minh Tran
Priority: Minor


Hello

I’m using camel 2.16.2 and I’m finding the bean parameter binding doesn’t seem 
to work very well on overloaded methods. See below for an example

{noformat}
public class ClassA {
public int foo() {
return 0;
}

public int foo(String param1) {
return 1;
}

public int foo(String param1, String param2) {
return 2;
}

public int foo(String param1, ClassB param2) {
return 3;
}

public int foo(boolean param1, String param2) {
return 4;
}
}

public class ClassB {

}
{noformat}

Here are the routes

{noformat}
from("direct:noParam").bean(ClassA.class, "foo()").to("mock:end");
from("direct:1Param").bean(ClassA.class, "foo(${body})").to("mock:end");
from("direct:2Param").bean(ClassA.class, "foo(${body}, 
${header.key})").to("mock:end”);
{noformat}

And here are the tests

{noformat}
@EndpointInject(uri = "mock:end")
private MockEndpoint end;

@Produce
private ProducerTemplate producerTemplate;

@Test
// passes
public void testNoParam() throws InterruptedException {
end.expectedBodiesReceived(0);
producerTemplate.sendBodyAndHeader("direct:noParam", "body", 
"key", "value");
end.assertIsSatisfied();
}

@Test
// passes
public void test1Param() throws InterruptedException {
end.expectedBodiesReceived(1);
producerTemplate.sendBodyAndHeader("direct:1Param", "body", 
"key", "value");
end.assertIsSatisfied();
}

@Test
// throws ambiguous method call exception
public void test2Param_string() throws InterruptedException {
end.expectedBodiesReceived(2);
producerTemplate.sendBodyAndHeader("direct:2Param", "body", 
"key", "value");
end.assertIsSatisfied();
}

@Test
// throws ambiguous method call exception
public void test2Param_classB() throws InterruptedException {
end.expectedBodiesReceived(3);
producerTemplate.sendBodyAndHeader("direct:2Param", "body", 
"key", new ClassB());
end.assertIsSatisfied();
}

@Test
// passes
public void test2Param_boolBody() throws InterruptedException {
end.expectedBodiesReceived(4);
producerTemplate.sendBodyAndHeader("direct:2Param", true, 
"key", "value");
end.assertIsSatisfied();
}
{noformat}

I don’t understand why test2Param_string and test2Param_classB throw ambiguous 
call exceptions. Here’s a sample stack trace.

{noformat}
org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous method 
invocations possible: [public int 
au.com.winning.navmidware.routes.navws.ClassA.foo(java.lang.String,java.lang.String),
 public int 
au.com.winning.navmidware.routes.navws.ClassA.foo(java.lang.String,au.com.winning.navmidware.routes.navws.ClassB)].
 Exchange[ID-minhmac-local-53614-1457474273519-0-2][Message: body]
at 
org.apache.camel.component.bean.BeanInfo.chooseBestPossibleMethodInfo(BeanInfo.java:835)
 ~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.component.bean.BeanInfo.chooseMethodWithMatchingBody(BeanInfo.java:764)
 ~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.component.bean.BeanInfo.chooseMethod(BeanInfo.java:621) 
~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:254) 
~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:183) 
~[camel-core-2.16.2.jar:2.16.2]
{noformat}

>From looking at the code in BeanInfo, I *think* it just tries to match the 
>type on the body and if it sees multiple possible methods then it throws the 
>exception. I believe it should go further and try to match the type on the 
>other parameters as well?

To get around this issue temporarily, I’ve had to write an adapter class that 
wraps around ClassA but it’s not an ideal solution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9689) Websocket Component Failing to Install in Karaf

[Trey Sargent (JIRA)]

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

Trey Sargent updated CAMEL-9689:

Description: 
When installing the camel-websocket component in Karaf 4.0.4 the process fails 
with the following message:

Error executing command: Unable to resolve javax.mail/1.4.5: missing 
requirement [javax.mail/1.4.5] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=com.sun.mail.handlers)(version>=1.4.0))"

  was:When installing the camel-websocket component in Karaf 4.0.4 the process 
hangs.


> Websocket Component Failing to Install in Karaf
> ---
>
> Key: CAMEL-9689
> URL: https://issues.apache.org/jira/browse/CAMEL-9689
> Project: Camel
>  Issue Type: Bug
>  Components: camel-websocket
>Affects Versions: 2.16.2
> Environment: Oracle Java 8, Apache Karaf 4.0.4
>Reporter: Trey Sargent
>Priority: Critical
>
> When installing the camel-websocket component in Karaf 4.0.4 the process 
> fails with the following message:
> Error executing command: Unable to resolve javax.mail/1.4.5: missing 
> requirement [javax.mail/1.4.5] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=com.sun.mail.handlers)(version>=1.4.0))"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9689) Websocket Component Failing to Install in Karaf

[Trey Sargent (JIRA)]

Trey Sargent created CAMEL-9689:
---

 Summary: Websocket Component Failing to Install in Karaf
 Key: CAMEL-9689
 URL: https://issues.apache.org/jira/browse/CAMEL-9689
 Project: Camel
  Issue Type: Bug
  Components: camel-websocket
Affects Versions: 2.16.2
 Environment: Oracle Java 8, Apache Karaf 4.0.4
Reporter: Trey Sargent
Priority: Critical


When installing the camel-websocket component in Karaf 4.0.4 the process hangs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9688) Documentation: Wrong header name on smpp wiki page

[Pascal Schumacher (JIRA)]

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

Pascal Schumacher updated CAMEL-9688:
-
Description: There is a small error on the 
http://camel.apache.org/smpp.html wiki page. At least in 2.16.2 and current 
master there is no header called "CamelSmppFinalStatus", the header is called 
"CamelSmppStatus" (see: 
https://github.com/apache/camel/blob/cc9924f41965885af25027fc053adaf21f15b5b4/components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConstants.java#L41)
  (was: There is a small error on the http://camel.apache.org/smpp.html at 
least in 2.16.2 and current master there is no header called 
"CamelSmppFinalStatus", the header is called "CamelSmppStatus" (see: 
https://github.com/apache/camel/blob/cc9924f41965885af25027fc053adaf21f15b5b4/components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConstants.java#L41))

> Documentation: Wrong header name on smpp wiki page
> --
>
> Key: CAMEL-9688
> URL: https://issues.apache.org/jira/browse/CAMEL-9688
> Project: Camel
>  Issue Type: Bug
>  Components: camel-smpp, documentation
>Affects Versions: 2.16.2
>Reporter: Pascal Schumacher
>Priority: Minor
>
> There is a small error on the http://camel.apache.org/smpp.html wiki page. At 
> least in 2.16.2 and current master there is no header called 
> "CamelSmppFinalStatus", the header is called "CamelSmppStatus" (see: 
> https://github.com/apache/camel/blob/cc9924f41965885af25027fc053adaf21f15b5b4/components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConstants.java#L41)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9688) Documentation: Wrong header name on smpp wiki page

[Pascal Schumacher (JIRA)]

Pascal Schumacher created CAMEL-9688:


 Summary: Documentation: Wrong header name on smpp wiki page
 Key: CAMEL-9688
 URL: https://issues.apache.org/jira/browse/CAMEL-9688
 Project: Camel
  Issue Type: Bug
  Components: camel-smpp, documentation
Affects Versions: 2.16.2
Reporter: Pascal Schumacher
Priority: Minor


There is a small error on the http://camel.apache.org/smpp.html at least in 
2.16.2 and current master there is no header called "CamelSmppFinalStatus", the 
header is called "CamelSmppStatus" (see: 
https://github.com/apache/camel/blob/cc9924f41965885af25027fc053adaf21f15b5b4/components/camel-smpp/src/main/java/org/apache/camel/component/smpp/SmppConstants.java#L41)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9687) camel-swagger - Should use resolved placeholders in output

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-9687:
---
Priority: Minor  (was: Major)

> camel-swagger - Should use resolved placeholders in output
> --
>
> Key: CAMEL-9687
> URL: https://issues.apache.org/jira/browse/CAMEL-9687
> Project: Camel
>  Issue Type: Bug
>  Components: camel-swagger
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/camel-swagger-java-not-parse-property-tp5778734.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9687) camel-swagger - Should use resolved placeholders in output

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-9687:
--

 Summary: camel-swagger - Should use resolved placeholders in output
 Key: CAMEL-9687
 URL: https://issues.apache.org/jira/browse/CAMEL-9687
 Project: Camel
  Issue Type: Bug
  Components: camel-swagger
Affects Versions: 2.16.2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.16.3, 2.17.0


See nabble
http://camel.465427.n5.nabble.com/camel-swagger-java-not-parse-property-tp5778734.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-9497:
---
Component/s: camel-spring-ws

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-ws
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli edited comment on CAMEL-9497 at 3/9/16 2:43 PM:


[~davsclaus] I'm a little confused by 
org.apache.camel.component.spring.ws.type.EndpointMappingKey which should be an 
UriParam:

{code:java}
@UriParam(label = "consumer")
private EndpointMappingKey endpointMappingKey;

public EndpointMappingKey getEndpointMappingKey() {
return endpointMappingKey;
}

public void setEndpointMappingKey(EndpointMappingKey endpointMappingKey) {
this.endpointMappingKey = endpointMappingKey;
}
{code}

But then it appears that it is instantiated by 
SpringWebserviceComponent#addConsumerConfiguration where any value you may have 
set will be overridden:

{code:java}


private void addConsumerConfiguration(String remaining, Map 
parameters, SpringWebserviceConfiguration configuration) {
EndpointMappingType type = 
EndpointMappingType.getTypeFromUriPrefix(remaining);
if (type != null) {
LOG.debug("Building Spring Web Services consumer of type " + type);
String lookupKey = getLookupKey(remaining, type);
if (EndpointMappingType.BEANNAME.equals(type)) {
addEndpointDispatcherToConfiguration(configuration, lookupKey);
} else {
addEndpointMappingToConfiguration(parameters, configuration);
}
XPathExpression xPathExpression = null;
if (type.equals(EndpointMappingType.XPATHRESULT)) {
String expression = getAndRemoveParameter(parameters, 
"expression", String.class);
configuration.setExpression(expression);
xPathExpression = createXPathExpression(expression);
}
configuration.setEndpointMappingKey(new EndpointMappingKey(type, 
lookupKey, xPathExpression));
}
}
{code}

Am I wrong ? 






was (Author: lb):
[~davsclaus] I'm a little confused by 
org.apache.camel.component.spring.ws.type.EndpointMappingKey which should be an 
UriParam:

{code:java}
@UriParam(label = "consumer")
private EndpointMappingKey endpointMappingKey;

public EndpointMappingKey getEndpointMappingKey() {
return endpointMappingKey;
}

public void setEndpointMappingKey(EndpointMappingKey endpointMappingKey) {
this.endpointMappingKey = endpointMappingKey;
}
{code}

But then it appears that it is instantiated by 
SpringWebserviceComponent#addConsumerConfiguration where any value you may have 
set will be overridden, am I wrong ? 





> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli commented on CAMEL-9497:


[~davsclaus] I'm a little confused by 
org.apache.camel.component.spring.ws.type.EndpointMappingKey which should be an 
UriParam:

{code:java}
@UriParam(label = "consumer")
private EndpointMappingKey endpointMappingKey;

public EndpointMappingKey getEndpointMappingKey() {
return endpointMappingKey;
}

public void setEndpointMappingKey(EndpointMappingKey endpointMappingKey) {
this.endpointMappingKey = endpointMappingKey;
}
{code}

But then it appears that it is instantiated by 
SpringWebserviceComponent#addConsumerConfiguration where any value you may have 
set will be overridden, am I wrong ? 





> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9523) Use setStopRow on org.apache.hadoop.hbase.client.Scan

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated CAMEL-9523:

Fix Version/s: 2.17.0

> Use setStopRow on org.apache.hadoop.hbase.client.Scan
> -
>
> Key: CAMEL-9523
> URL: https://issues.apache.org/jira/browse/CAMEL-9523
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-hbase
>Affects Versions: 2.15.2
> Environment: Fuse 6.2.1 on JBOSS EAP 6.4.4
>Reporter: Matteo Perini
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.17.0
>
>
> Add the feature to stop the scan of hbase table at fixed key



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9523) Use setStopRow on org.apache.hadoop.hbase.client.Scan

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved CAMEL-9523.
-
Resolution: Fixed

> Use setStopRow on org.apache.hadoop.hbase.client.Scan
> -
>
> Key: CAMEL-9523
> URL: https://issues.apache.org/jira/browse/CAMEL-9523
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-hbase
>Affects Versions: 2.15.2
> Environment: Fuse 6.2.1 on JBOSS EAP 6.4.4
>Reporter: Matteo Perini
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.17.0
>
>
> Add the feature to stop the scan of hbase table at fixed key



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9686) camel-aws - Using cron scheduler on aws-s3 do not work

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9686.

Resolution: Fixed

> camel-aws - Using cron scheduler on aws-s3 do not work
> --
>
> Key: CAMEL-9686
> URL: https://issues.apache.org/jira/browse/CAMEL-9686
> Project: Camel
>  Issue Type: Bug
>  Components: camel-aws
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.16.3, 2.17.0
>
>
> See SO
> http://stackoverflow.com/questions/35865863/camel-aws-s3-cron-schedule



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9686) camel-aws - Using cron scheduler on aws-s3 do not work

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-9686:
--

 Summary: camel-aws - Using cron scheduler on aws-s3 do not work
 Key: CAMEL-9686
 URL: https://issues.apache.org/jira/browse/CAMEL-9686
 Project: Camel
  Issue Type: Bug
  Components: camel-aws
Affects Versions: 2.16.2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.16.3, 2.17.0


See SO
http://stackoverflow.com/questions/35865863/camel-aws-s3-cron-schedule



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

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

Work on CAMEL-9497 started by Luca Burgazzoli.
--
> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli reassigned CAMEL-9497:
--

Assignee: Luca Burgazzoli

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9497:


Yeah Luca, the source code is *right* and the website wiki is outdated / wrong.


> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9513) Upgrade the Servlet API to 3.1

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved CAMEL-9513.
-
   Resolution: Fixed
Fix Version/s: (was: 2.18.0)
   2.17.0

> Upgrade the Servlet API to 3.1
> --
>
> Key: CAMEL-9513
> URL: https://issues.apache.org/jira/browse/CAMEL-9513
> Project: Camel
>  Issue Type: Task
>  Components: camel-http, camel-http-common, camel-jetty, camel-servlet
>Reporter: Willem Jiang
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli commented on CAMEL-9497:


[~davsclaus] is it only a matter of documentation ? I so I can take it

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9684) camel-infinispan : add support for setting query builder in InifispanConfiguration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-9684:
---

GitHub user lburgazzoli opened a pull request:

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

CAMEL-9684 - camel-infinispan : add support for setting query builder…

… in InifispanConfiguration

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

$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-9684

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

https://github.com/apache/camel/pull/891.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 #891


commit 2d6140d3723a75d7d2e4286589d194aadb19445a
Author: lburgazzoli 
Date:   2016-03-09T11:35:36Z

CAMEL-9684 - camel-infinispan : add support for setting query builder in 
InifispanConfiguration




> camel-infinispan : add support for setting query builder in 
> InifispanConfiguration
> --
>
> Key: CAMEL-9684
> URL: https://issues.apache.org/jira/browse/CAMEL-9684
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9680) Stream caching is broken under Spring Boot

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9680:


You can turn off this type converter with setting in your app properties

camel.springboot.typeConversion=false

> Stream caching is broken under Spring Boot
> --
>
> Key: CAMEL-9680
> URL: https://issues.apache.org/jira/browse/CAMEL-9680
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>Assignee: Claus Ibsen
> Fix For: 2.16.3, 2.17.0
>
>
> As documented in the [camel-spring-boot 
> documentation|https://camel.apache.org/spring-boot.html], camel-spring-boot 
> will delegate type conversion to Spring by default (see 
> {{org.apache.camel.spring.boot.TypeConversionConfiguration}}). Whenever the 
> body of a route changes to a List, Spring believes it can convert it and 
> fails. See the supplied test.
> The runs correctly if the {{SpringTypeConverter}} is removed.
> {code:java|title=StreamCachingTest.java}
> package com.example.bugs;
> import org.apache.camel.CamelContext;
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.spring.boot.SpringTypeConverter;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> import 
> org.springframework.boot.autoconfigure.condition.ConditionalOnMissingBean;
> import org.springframework.context.ApplicationContext;
> import org.springframework.context.annotation.Bean;
> import org.springframework.core.convert.ConversionService;
> import org.springframework.core.convert.converter.Converter;
> import org.springframework.core.convert.support.DefaultConversionService;
> import java.io.File;
> import java.io.FileInputStream;
> import java.util.List;
> import static java.util.Arrays.asList;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> 
> context.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter(context,
>  new ConversionService[]{new DefaultConversionService()}), true);
> from("direct:foo")
> .streamCaching()
> .bean(MyBean.class)
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> template.sendBody("direct:foo", new FileInputStream(new 
> File("src/main/resources/banner.txt")));
> endOfRoute.assertIsSatisfied();
> }
> public static class MyBean {
> public List someNumbers() {
> return asList(1, 2, 3);
> }
> }
> /**
>  * Copied from org.apache.camel.spring.boot.TypeConversionConfiguration 
> (they are package protected)
>  **/
> @Bean
> SpringTypeConverter springTypeConverter(CamelContext camelContext, 
> ConversionService[] conversionServices) {
> SpringTypeConverter springTypeConverter = new 
> SpringTypeConverter(asList(conversionServices));
> 
> camelContext.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter,
>  true);
> return springTypeConverter;
> }
> @ConditionalOnMissingBean
> @Bean
> ConversionService defaultCamelConversionService(ApplicationContext 
> applicationContext) {
> DefaultConversionService service = new DefaultConversionService();
> for (Converter converter : 
> applicationContext.getBeansOfType(Converter.class).values()) {
> service.addConverter(converter);
> }
> return service;
> }
> }
> {code}
> Result:
> {code:none}
> org.apache.camel.CamelExecutionException: Exception occurred during execution 
> on the exchange: Exchange[ID-CAW811-53239-1457446127171-0-2][Message: 1,2,3]
>   at 
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1658)
>   at 
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:646)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
>   at 
> 

[jira] [Assigned] (CAMEL-9680) Stream caching is broken under Spring Boot

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-9680:
--

Assignee: Claus Ibsen

> Stream caching is broken under Spring Boot
> --
>
> Key: CAMEL-9680
> URL: https://issues.apache.org/jira/browse/CAMEL-9680
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>Assignee: Claus Ibsen
> Fix For: 2.16.3, 2.17.0
>
>
> As documented in the [camel-spring-boot 
> documentation|https://camel.apache.org/spring-boot.html], camel-spring-boot 
> will delegate type conversion to Spring by default (see 
> {{org.apache.camel.spring.boot.TypeConversionConfiguration}}). Whenever the 
> body of a route changes to a List, Spring believes it can convert it and 
> fails. See the supplied test.
> The runs correctly if the {{SpringTypeConverter}} is removed.
> {code:java|title=StreamCachingTest.java}
> package com.example.bugs;
> import org.apache.camel.CamelContext;
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.spring.boot.SpringTypeConverter;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> import 
> org.springframework.boot.autoconfigure.condition.ConditionalOnMissingBean;
> import org.springframework.context.ApplicationContext;
> import org.springframework.context.annotation.Bean;
> import org.springframework.core.convert.ConversionService;
> import org.springframework.core.convert.converter.Converter;
> import org.springframework.core.convert.support.DefaultConversionService;
> import java.io.File;
> import java.io.FileInputStream;
> import java.util.List;
> import static java.util.Arrays.asList;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> 
> context.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter(context,
>  new ConversionService[]{new DefaultConversionService()}), true);
> from("direct:foo")
> .streamCaching()
> .bean(MyBean.class)
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> template.sendBody("direct:foo", new FileInputStream(new 
> File("src/main/resources/banner.txt")));
> endOfRoute.assertIsSatisfied();
> }
> public static class MyBean {
> public List someNumbers() {
> return asList(1, 2, 3);
> }
> }
> /**
>  * Copied from org.apache.camel.spring.boot.TypeConversionConfiguration 
> (they are package protected)
>  **/
> @Bean
> SpringTypeConverter springTypeConverter(CamelContext camelContext, 
> ConversionService[] conversionServices) {
> SpringTypeConverter springTypeConverter = new 
> SpringTypeConverter(asList(conversionServices));
> 
> camelContext.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter,
>  true);
> return springTypeConverter;
> }
> @ConditionalOnMissingBean
> @Bean
> ConversionService defaultCamelConversionService(ApplicationContext 
> applicationContext) {
> DefaultConversionService service = new DefaultConversionService();
> for (Converter converter : 
> applicationContext.getBeansOfType(Converter.class).values()) {
> service.addConverter(converter);
> }
> return service;
> }
> }
> {code}
> Result:
> {code:none}
> org.apache.camel.CamelExecutionException: Exception occurred during execution 
> on the exchange: Exchange[ID-CAW811-53239-1457446127171-0-2][Message: 1,2,3]
>   at 
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1658)
>   at 
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:646)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:139)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:144)
>  

[jira] [Commented] (CAMEL-9680) Stream caching is broken under Spring Boot

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9680:


Okay its a bug in spring type converter where it returns true in the canConvert 
method, and then fail just right after calling convert. 

I am going to skip stream cache types.

> Stream caching is broken under Spring Boot
> --
>
> Key: CAMEL-9680
> URL: https://issues.apache.org/jira/browse/CAMEL-9680
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
> Fix For: 2.16.3, 2.17.0
>
>
> As documented in the [camel-spring-boot 
> documentation|https://camel.apache.org/spring-boot.html], camel-spring-boot 
> will delegate type conversion to Spring by default (see 
> {{org.apache.camel.spring.boot.TypeConversionConfiguration}}). Whenever the 
> body of a route changes to a List, Spring believes it can convert it and 
> fails. See the supplied test.
> The runs correctly if the {{SpringTypeConverter}} is removed.
> {code:java|title=StreamCachingTest.java}
> package com.example.bugs;
> import org.apache.camel.CamelContext;
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.spring.boot.SpringTypeConverter;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> import 
> org.springframework.boot.autoconfigure.condition.ConditionalOnMissingBean;
> import org.springframework.context.ApplicationContext;
> import org.springframework.context.annotation.Bean;
> import org.springframework.core.convert.ConversionService;
> import org.springframework.core.convert.converter.Converter;
> import org.springframework.core.convert.support.DefaultConversionService;
> import java.io.File;
> import java.io.FileInputStream;
> import java.util.List;
> import static java.util.Arrays.asList;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> 
> context.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter(context,
>  new ConversionService[]{new DefaultConversionService()}), true);
> from("direct:foo")
> .streamCaching()
> .bean(MyBean.class)
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> template.sendBody("direct:foo", new FileInputStream(new 
> File("src/main/resources/banner.txt")));
> endOfRoute.assertIsSatisfied();
> }
> public static class MyBean {
> public List someNumbers() {
> return asList(1, 2, 3);
> }
> }
> /**
>  * Copied from org.apache.camel.spring.boot.TypeConversionConfiguration 
> (they are package protected)
>  **/
> @Bean
> SpringTypeConverter springTypeConverter(CamelContext camelContext, 
> ConversionService[] conversionServices) {
> SpringTypeConverter springTypeConverter = new 
> SpringTypeConverter(asList(conversionServices));
> 
> camelContext.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter,
>  true);
> return springTypeConverter;
> }
> @ConditionalOnMissingBean
> @Bean
> ConversionService defaultCamelConversionService(ApplicationContext 
> applicationContext) {
> DefaultConversionService service = new DefaultConversionService();
> for (Converter converter : 
> applicationContext.getBeansOfType(Converter.class).values()) {
> service.addConverter(converter);
> }
> return service;
> }
> }
> {code}
> Result:
> {code:none}
> org.apache.camel.CamelExecutionException: Exception occurred during execution 
> on the exchange: Exchange[ID-CAW811-53239-1457446127171-0-2][Message: 1,2,3]
>   at 
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1658)
>   at 
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:646)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
>   at 
> 

[jira] [Work started] (CAMEL-9684) camel-infinispan : add support for setting query builder in InifispanConfiguration

[Luca Burgazzoli (JIRA)]

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

Work on CAMEL-9684 started by Luca Burgazzoli.
--
> camel-infinispan : add support for setting query builder in 
> InifispanConfiguration
> --
>
> Key: CAMEL-9684
> URL: https://issues.apache.org/jira/browse/CAMEL-9684
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9685) camel-infinispan : support continuous query in consumer

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-9685:
--

 Summary: camel-infinispan : support continuous query in consumer
 Key: CAMEL-9685
 URL: https://issues.apache.org/jira/browse/CAMEL-9685
 Project: Camel
  Issue Type: New Feature
  Components: camel-infinispan
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9619) Qpid failover unsuccessful, Invalid Bundle Context

[Sergey (JIRA)]

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

Sergey  commented on CAMEL-9619:


This is possible root cause of an issue (i.e., bug in qpid client):

{code}
Exception in thread "Dispatcher-0-Conn-167" 
org.apache.qpid.transport.SessionException: Command was interrupted because of 
failover, before being sent
at 
org.apache.qpid.transport.Session.checkFailoverRequired(Session.java:826)
at org.apache.qpid.transport.Session.invoke(Session.java:658)
at org.apache.qpid.transport.Session.invoke(Session.java:627)
at 
org.apache.qpid.transport.SessionInvoker.messageRelease(SessionInvoker.java:105)
at 
org.apache.qpid.client.AMQSession_0_10.rejectMessage(AMQSession_0_10.java:545)
at org.apache.qpid.client.AMQSession.rejectMessage(AMQSession.java:1839)
at 
org.apache.qpid.client.AMQSession$Dispatcher.notifyConsumer(AMQSession.java:3541)
at 
org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java:3485)
at 
org.apache.qpid.client.AMQSession$Dispatcher.access$1000(AMQSession.java:3261)
at org.apache.qpid.client.AMQSession.dispatch(AMQSession.java:3254)
at 
org.apache.qpid.client.message.UnprocessedMessage.dispatch(UnprocessedMessage.java:54)
at 
org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:3403)
at java.lang.Thread.run(Thread.java:745)
{code}

> Qpid failover unsuccessful, Invalid Bundle Context
> --
>
> Key: CAMEL-9619
> URL: https://issues.apache.org/jira/browse/CAMEL-9619
> Project: Camel
>  Issue Type: Bug
>  Components: camel-amqp, osgi
>Affects Versions: 2.15.2
>Reporter: Sergey 
>Priority: Minor
> Attachments: camel-context.xml, jms.xml, osgi-context.xml
>
>
> We have AMQP camel client consuming data from Qpid queue. Our setup contains 
> one camel bundle and a connection factory, deployed as spring-dm xml. 
> Everything works fine until failover, when we have an error like this:
> 2016-02-18 18:00:05,273 | ERROR | [fibigdataQueue] | 
> faultJmsMessageListenerContainer | 292 - 
> org.apache.servicemix.bundles.spring-jms - 3.2.11.RELEASE_1 | Could not 
> refresh JMS Connection for destination 'fibigdataQueue' - retrying in 5000 
> ms. Cause: Invalid BundleContext.
> At the moment camel stops to consume messages from queue, and stuck in this 
> state until camel bundle updated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9680) Stream caching is broken under Spring Boot

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9680:


[~hekonsek] do you remember what value-add the spring type converters would 
give us? 

> Stream caching is broken under Spring Boot
> --
>
> Key: CAMEL-9680
> URL: https://issues.apache.org/jira/browse/CAMEL-9680
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
> Fix For: 2.16.3, 2.17.0
>
>
> As documented in the [camel-spring-boot 
> documentation|https://camel.apache.org/spring-boot.html], camel-spring-boot 
> will delegate type conversion to Spring by default (see 
> {{org.apache.camel.spring.boot.TypeConversionConfiguration}}). Whenever the 
> body of a route changes to a List, Spring believes it can convert it and 
> fails. See the supplied test.
> The runs correctly if the {{SpringTypeConverter}} is removed.
> {code:java|title=StreamCachingTest.java}
> package com.example.bugs;
> import org.apache.camel.CamelContext;
> import org.apache.camel.EndpointInject;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.spring.boot.SpringTypeConverter;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.junit.Test;
> import 
> org.springframework.boot.autoconfigure.condition.ConditionalOnMissingBean;
> import org.springframework.context.ApplicationContext;
> import org.springframework.context.annotation.Bean;
> import org.springframework.core.convert.ConversionService;
> import org.springframework.core.convert.converter.Converter;
> import org.springframework.core.convert.support.DefaultConversionService;
> import java.io.File;
> import java.io.FileInputStream;
> import java.util.List;
> import static java.util.Arrays.asList;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> 
> context.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter(context,
>  new ConversionService[]{new DefaultConversionService()}), true);
> from("direct:foo")
> .streamCaching()
> .bean(MyBean.class)
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> template.sendBody("direct:foo", new FileInputStream(new 
> File("src/main/resources/banner.txt")));
> endOfRoute.assertIsSatisfied();
> }
> public static class MyBean {
> public List someNumbers() {
> return asList(1, 2, 3);
> }
> }
> /**
>  * Copied from org.apache.camel.spring.boot.TypeConversionConfiguration 
> (they are package protected)
>  **/
> @Bean
> SpringTypeConverter springTypeConverter(CamelContext camelContext, 
> ConversionService[] conversionServices) {
> SpringTypeConverter springTypeConverter = new 
> SpringTypeConverter(asList(conversionServices));
> 
> camelContext.getTypeConverterRegistry().addFallbackTypeConverter(springTypeConverter,
>  true);
> return springTypeConverter;
> }
> @ConditionalOnMissingBean
> @Bean
> ConversionService defaultCamelConversionService(ApplicationContext 
> applicationContext) {
> DefaultConversionService service = new DefaultConversionService();
> for (Converter converter : 
> applicationContext.getBeansOfType(Converter.class).values()) {
> service.addConverter(converter);
> }
> return service;
> }
> }
> {code}
> Result:
> {code:none}
> org.apache.camel.CamelExecutionException: Exception occurred during execution 
> on the exchange: Exchange[ID-CAW811-53239-1457446127171-0-2][Message: 1,2,3]
>   at 
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1658)
>   at 
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:646)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
>   at 
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:139)
>   at 
> 

[jira] [Resolved] (CAMEL-9467) Camel-Kafka: Upgrade to kafka 0.9 and use the Java client instead of Scala

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-9467.

Resolution: Fixed

Thanks.

We should redo this documentation when it auto generates all those options. I 
am not gonna waste so much time maintaining the wiki stuff.

> Camel-Kafka: Upgrade to kafka 0.9 and use the Java client instead of Scala
> --
>
> Key: CAMEL-9467
> URL: https://issues.apache.org/jira/browse/CAMEL-9467
> Project: Camel
>  Issue Type: Task
>  Components: camel-kafka
>Reporter: Andrea Cosentino
>Assignee: Claus Ibsen
> Fix For: 2.17.0
>
> Attachments: Kafka Component WIKI.docx, camel-kafka-Anbu.zip, 
> camel-kafka-callback.zip, camel-kafka-claus.zip, camel-kafka.zip, 
> camel-kafka.zip
>
>
> From release 0.9.0.0 the Kafka Consumer/Producer configuration properties 
> seems to be changed a little.
> Also we have to use the new Java implementation of Kafka Producer/Consumer, 
> actually we are using the Scala version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9467) Camel-Kafka: Upgrade to kafka 0.9 and use the Java client instead of Scala

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-9467:


Thanks Andu, I am working on merging your changes.

> Camel-Kafka: Upgrade to kafka 0.9 and use the Java client instead of Scala
> --
>
> Key: CAMEL-9467
> URL: https://issues.apache.org/jira/browse/CAMEL-9467
> Project: Camel
>  Issue Type: Task
>  Components: camel-kafka
>Reporter: Andrea Cosentino
>Assignee: Claus Ibsen
> Fix For: 2.17.0
>
> Attachments: Kafka Component WIKI.docx, camel-kafka-Anbu.zip, 
> camel-kafka-callback.zip, camel-kafka-claus.zip, camel-kafka.zip, 
> camel-kafka.zip
>
>
> From release 0.9.0.0 the Kafka Consumer/Producer configuration properties 
> seems to be changed a little.
> Also we have to use the new Java implementation of Kafka Producer/Consumer, 
> actually we are using the Scala version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-9467) Camel-Kafka: Upgrade to kafka 0.9 and use the Java client instead of Scala

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-9467:
--

Assignee: Claus Ibsen  (was: Andrea Cosentino)

> Camel-Kafka: Upgrade to kafka 0.9 and use the Java client instead of Scala
> --
>
> Key: CAMEL-9467
> URL: https://issues.apache.org/jira/browse/CAMEL-9467
> Project: Camel
>  Issue Type: Task
>  Components: camel-kafka
>Reporter: Andrea Cosentino
>Assignee: Claus Ibsen
> Fix For: 2.17.0
>
> Attachments: Kafka Component WIKI.docx, camel-kafka-Anbu.zip, 
> camel-kafka-callback.zip, camel-kafka-claus.zip, camel-kafka.zip, 
> camel-kafka.zip
>
>
> From release 0.9.0.0 the Kafka Consumer/Producer configuration properties 
> seems to be changed a little.
> Also we have to use the new Java implementation of Kafka Producer/Consumer, 
> actually we are using the Scala version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9681) Add an option to enable/disable cache creation

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-9681.

   Resolution: Fixed
Fix Version/s: 2.17.0

> Add an option to enable/disable cache creation
> --
>
> Key: CAMEL-9681
> URL: https://issues.apache.org/jira/browse/CAMEL-9681
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-jcache
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)