[jira] [Created] (CAMEL-9007) Contributing Zipkin / Brave support to Camel.next

2015-07-24 Thread Andrew Harmel-Law (JIRA)
Andrew Harmel-Law created CAMEL-9007:


 Summary: Contributing Zipkin / Brave support to Camel.next
 Key: CAMEL-9007
 URL: https://issues.apache.org/jira/browse/CAMEL-9007
 Project: Camel
  Issue Type: Wish
Affects Versions: Future
Reporter: Andrew Harmel-Law


Hi,

We're building Microservices with Camel, predominantly producing from REST DSL 
components and have got to the point where having easy support for Zipkin[1] / 
Brave [2] would be of great help.

We wondered if this was already on the cards for a future release, and if we 
might be able to work on it, and if not, if it would be something we could work 
on and contribute (with guidance to smooth the design and implementation)?

Kind regards, the Capgemini UK and Indian Camel teams

[1] https://github.com/openzipkin/zipkin
[2] https://github.com/openzipkin/brave



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


[jira] [Created] (CAMEL-9008) Contributing GRPC / Thrift support to Camel.next

2015-07-24 Thread Andrew Harmel-Law (JIRA)
Andrew Harmel-Law created CAMEL-9008:


 Summary: Contributing GRPC / Thrift support to Camel.next
 Key: CAMEL-9008
 URL: https://issues.apache.org/jira/browse/CAMEL-9008
 Project: Camel
  Issue Type: Wish
Affects Versions: Future
Reporter: Andrew Harmel-Law


Hi,

We're building Microservices with Camel, predominantly producing from REST DSL 
components and have got to the point where having an easy way to swap in GRPC 
[1] / Thrift [2] endpoints and clients would be of great help.

We wondered if this was already on the cards for a future release, and if we 
might be able to work on it, and if not, if it would be something we could work 
on and contribute (with guidance to smooth the design and implementation)?

Kind regards, the Capgemini UK and Indian Camel teams
[1] http://www.grpc.io/
[2] https://thrift.apache.org/



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


[jira] [Updated] (CAMEL-8996) camel-undertow - Add support for Exchange.HTTP_QUERY

2015-07-24 Thread Claus Ibsen (JIRA)

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

Claus Ibsen updated CAMEL-8996:
---
Summary: camel-undertow - Add support for Exchange.HTTP_QUERY  (was: Add 
support for Exchange.HTTP_QUERY)

 camel-undertow - Add support for Exchange.HTTP_QUERY
 

 Key: CAMEL-8996
 URL: https://issues.apache.org/jira/browse/CAMEL-8996
 Project: Camel
  Issue Type: New Feature
  Components: camel-undertow
Reporter: Thomas Diesler
Assignee: Claus Ibsen
 Fix For: 2.16.0


 Component camel-undertow
 Add support for 
 {code}
 ProducerTemplate producer = camelctx.createProducerTemplate();
 String result = producer.requestBodyAndHeader(direct:start, 
 null, Exchange.HTTP_QUERY, name=Kermit, String.class);
 Assert.assertEquals(Hello Kermit, result);
 {code}
 and possibly other headers. This works for camel-http4



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


[jira] [Created] (CAMEL-9009) Camel RSS module should support basic authentication

2015-07-24 Thread Alexander Friedrichs (JIRA)
Alexander Friedrichs created CAMEL-9009:
---

 Summary: Camel RSS module should support basic authentication
 Key: CAMEL-9009
 URL: https://issues.apache.org/jira/browse/CAMEL-9009
 Project: Camel
  Issue Type: Wish
  Components: camel-rss
Affects Versions: Future
Reporter: Alexander Friedrichs
Priority: Minor


There is an question for Camel RSS module with basic authentication in  
[Stakoverflow|http://stackoverflow.com/questions/31567021/apache-camel-rss-module-with-basic-authentication].
It should not be so complicated, to supplement the function.



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


[jira] [Created] (CAMEL-9010) camel-stream - When using scanStream it should be able to deal if the file is deleted or not present

2015-07-24 Thread Claus Ibsen (JIRA)
Claus Ibsen created CAMEL-9010:
--

 Summary: camel-stream - When using scanStream it should be able to 
deal if the file is deleted or not present
 Key: CAMEL-9010
 URL: https://issues.apache.org/jira/browse/CAMEL-9010
 Project: Camel
  Issue Type: Improvement
  Components: camel-stream
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.16.0


See SO
http://stackoverflow.com/questions/31601385/read-file-line-by-line-as-soon-as-these-lines-appear-in-the-file-using-apache-ca?noredirect=1#comment51156841_31601385

We should support the use-case if the file is deleted then its temporary not 
available, and the consumer should just ignore this and try to read the stream 
on next poll.



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


[jira] [Commented] (CAMEL-7831) create a java8 only demo showing how to use lambda expressions for Predicate / Expression inside the Java DSL (using Message as a typesafe parameter)

2015-07-24 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640171#comment-14640171
 ] 

Claus Ibsen commented on CAMEL-7831:


Ah thanks for the heads up on the exchange. Maybe we can add to the java dsl an 
ObjectExpression that is returning an Object so the lambda can use that?

 create a java8 only demo showing how to use lambda expressions for Predicate 
 / Expression inside the Java DSL (using Message as a typesafe parameter)
 -

 Key: CAMEL-7831
 URL: https://issues.apache.org/jira/browse/CAMEL-7831
 Project: Camel
  Issue Type: New Feature
  Components: examples
Reporter: james strachan
 Fix For: 2.16.0


 e.g. so folks can type things like
 {code}
 from(seda:cheese).
   filter(m - m.getHeader(foo, int.class)  5).
   map(m - createPurchaseOrder(m.getBody(Invoice.class)).
   to(seda:bar);
 {code}
 Note if the current Predicate/Expression classes don't work as lambdas we 
 could add a new interface with a single method to the DSL to ensure Java 8 
 does the right thing with lambdas



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


[jira] [Created] (CAMEL-9013) Camel HTTP no longer supporting chunked transfer encoding with Tomcat

2015-07-24 Thread Bob Browning (JIRA)
Bob Browning created CAMEL-9013:
---

 Summary: Camel HTTP no longer supporting chunked transfer encoding 
with Tomcat
 Key: CAMEL-9013
 URL: https://issues.apache.org/jira/browse/CAMEL-9013
 Project: Camel
  Issue Type: Bug
  Components: camel-http, camel-servlet
Affects Versions: 2.15.2, 2.15.1, 2.15.0
Reporter: Bob Browning


When sending a chunked POST whilst running the servlet under Tomcat, camel now 
fails to read the input stream and sets the body to null.

[chunked-http-failure-test|https://github.com/ukcrpb6/chunked-http-failure-test]

This is due to camel checking the stream for available bytes introduced in 
CAMEL-5806. For whatever reason the CoyoteInputStream is returning 0 available 
bytes when handling a chunked request.

{code}
if (len  0) {
InputStream is = request.getInputStream();
if (is.available() == 0) {
// no data so return null
return null;
}
}
{code}




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


[jira] [Resolved] (CAMEL-9012) Olingo2's batch process generates the invalid request

2015-07-24 Thread Akitoshi Yoshida (JIRA)

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

Akitoshi Yoshida resolved CAMEL-9012.
-
   Resolution: Fixed
Fix Version/s: 2.15.3
   2.16.0

Updated the camel-olingo2 code to work with a newer olingo's odata2 2.0.x 
library and against the 2.0.0 and more recent servers.

In another ticket, I will add a more practical test to this component that does 
not require manually setting up a separate test server.
regards, aki

 Olingo2's batch process generates the invalid request
 -

 Key: CAMEL-9012
 URL: https://issues.apache.org/jira/browse/CAMEL-9012
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.15.2
Reporter: Akitoshi Yoshida
Assignee: Akitoshi Yoshida
 Fix For: 2.16.0, 2.15.3


 The syntax check of olingo2 lib was tighten from version 2.0.1.
 As a result, the batch message generated by camel-ollingo2's is rejected by 
 olingo2 version 2.0.1 and newer.
 Concretely, the current message includes two extra new lines within the batch 
 part that is rejected by the olingo2 library.
 OLINGO-739
 We should remove these two extra lines.



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


[jira] [Commented] (CAMEL-9009) Camel RSS module should support basic authentication

2015-07-24 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640435#comment-14640435
 ] 

Claus Ibsen commented on CAMEL-9009:


camel-atom and camel-rss. People is welcome to dive in and see what auth atom 
supports for this. 

 Camel RSS module should support basic authentication
 

 Key: CAMEL-9009
 URL: https://issues.apache.org/jira/browse/CAMEL-9009
 Project: Camel
  Issue Type: Wish
  Components: camel-rss
Affects Versions: Future
Reporter: Alexander Friedrichs
Priority: Minor

 There is an question for Camel RSS module with basic authentication in  
 [Stakoverflow|http://stackoverflow.com/questions/31567021/apache-camel-rss-module-with-basic-authentication].
 It should not be so complicated, to supplement the function.



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