Re: camel-kafka 2.16.2 -> 2.17.3

2016-11-22 Thread Tomohisa Igarashi
Is this what you're looking for? I think StringSerializer is used by default if you don't specify though. https://kafka.apache.org/090/javadoc/org/apache/kafka/common/serialization/StringSerializer.html On 11/23/2016 09:55 AM, catequil wrote: I have upgraded camel-kafka from 2.16.2 -> 2.17.3

camel-kafka 2.16.2 -> 2.17.3

2016-11-22 Thread catequil
I have upgraded camel-kafka from 2.16.2 -> 2.17.3 and I am having an issue with the serializerClass the above used to work, but now it is throwing the exception below: There is a lot of documentation on using the "kafka.serializer.StringEncoder" for kafka 0.8.2 or older, but nothing for

Re: Camel CXF - wrong Content-Type sent

2016-11-22 Thread Aki Yoshida
Umm. I don't know if the namespace for the soap binding is right. According to the online doc (https://cxf.apache.org/docs/schemas-and-namespaces.html), the namespace for the soap binding is http://cxf.apache.org/bindings/soap for both spring and blueprint. 2016-11-22 15:31 GMT+01:00

WS-SecurityPolicy and WS-Timestamp

2016-11-22 Thread martin.pelikan
Hi, I have a simple SOAP Proxy (input is non-secured, backend is secured by UsernameToken) in Spring, using Camel CXF and I would like to implement WS-Timestamp on producer endpoint. We are using WS-SecurityPolicy to authenticate against backend. As I understand there is one option - to leverage

Re: Camel CXF - wrong Content-Type sent

2016-11-22 Thread martin.pelikan
Manually editing WSDL and changing to (and all other elements with prefix 'soap') did the trick. Thanks for pushing me, Aki. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-wrong-Content-Type-sent-tp5790368p5790371.html Sent from the Camel - Users mailing list

Re: Camel CXF - wrong Content-Type sent

2016-11-22 Thread martin.pelikan
Hi Aki, I specified my question. You are correct about using WSDL v1.1. But set binding to SOAP1.2 did not help http://cxf.apache.org/blueprint/bindings/soap; /> Here is stack trace from Karaf: RouteId ProcessorId

Re: Camel CXF - wrong Content-Type sent

2016-11-22 Thread Aki Yoshida
you can't set the content-type in that way as the content-type is generated when the soap message is created. In other words, the content-type is determined by the soap protocol being used. I suppose your producer has the wsdl that uses SOAP 1.1 that assumes text/xml. To overwrite the soap

Camel CXF - wrong Content-Type sent

2016-11-22 Thread martin.pelikan
Hi all, I am trying to send SOAP request with Content-Type application/soap+xml. I call SOAPConsumer with correct header, in the middle of the route header is modified once again (to be sure), but in the end I get HTTP response '415: Cannot process the message because the content type 'text/xml;

Re: camel-swagger-servlet

2016-11-22 Thread Jonas Koperdraat
Thanks for you quick response, Claus. I was afraid of that. I'll look into the apiDocs=false option. Another solution would of course be to have to separate servlets and thereby two seperate Swagger servlets, but I'm not yet sure if that's worth the effort ;) Kind regards, Jonas Op di 22 nov.

use camel to send mail with word table

2016-11-22 Thread Deepak kumar
we have a data set in terms of json array. we want to send the json contents as word table data using apache camel. Can anyone please suggest how to achieve that? the data set looks like:- {"id":12,"name":"abc","age":25} {"id":13,"name":"xyz","age":26} {"id":12,"name":"mno","age":26}

Re: camel-swagger-servlet

2016-11-22 Thread Claus Ibsen
No you cannot have two versions. But I think there was a way to set that an api was internal using the swagger api to set apiDocs=false on the verbs you dont want On Tue, Nov 22, 2016 at 1:03 PM, Jonas Koperdraat wrote: > Hi, > > We have multiple REST API's documented

Contract first with Swagger and Camel

2016-11-22 Thread Pontus Ullgren
Hi. I'm looking in to the possibility to do Contract First development with Camel when the contract is a Swagger document. However I have been unable to find any good resources on this subject. So before we run of and build something I would like to check with the mailing list. How do you do

camel-swagger-servlet

2016-11-22 Thread Jonas Koperdraat
Hi, We have multiple REST API's documented with camel-swagger-servlet. These API's have some endpoints that are meant to be public and some that are meant to be private (or internal). Is it possible to filter the private endpoints from the Swagger documentation? And if so, is it possible to have

Re: Content Enricher example is wrong

2016-11-22 Thread Claus Ibsen
Hi Thanks I have updated the wiki page On Tue, Nov 22, 2016 at 11:27 AM, Alessandro Da Rugna wrote: > Hello, > I noticed that in the page http://camel.apache.org/mailing-lists.html > Spring DSL example for Camel 2.16 has invalid XML: > [quote] > The same example in

Content Enricher example is wrong

2016-11-22 Thread Alessandro Da Rugna
Hello, I noticed that in the page http://camel.apache.org/mailing-lists.html Spring DSL example for Camel 2.16 has invalid XML: [quote] The same example in the Spring DSL (Camel 2.16 or newer) http://camel.apache.org/schema/spring;> direct:resource ...

Re: Some notes I made on using Camel with Azure Service Bus

2016-11-22 Thread Claus Ibsen
Hi Frederik Thanks for sharing this with the Camel community. I have added a link to your blog on our link collection page http://camel.apache.org/articles On Tue, Nov 22, 2016 at 7:17 AM, Fredrik Jönsson wrote: > Hi, > > I haven’t seen many examples of this sort, so I thought I'd

Re: Handling Exceptions not handled by the DeadLetterChannelBuilder

2016-11-22 Thread Claus Ibsen
Hi See about the bridge error handler option http://camel.apache.org/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.html On Tue, Nov 22, 2016 at 5:10 AM, mayur_bm wrote: > Hi, > > i see that if component

Handling Exceptions not handled by the DeadLetterChannelBuilder

2016-11-22 Thread mayur_bm
Hi, i see that if component implements DefaultConsumer and its being run in the route & if it throws exception in application logic before an Exchange is created and we call the processor.process(exchange). its not being handled by the DeadLetterChannelBuilder ErrorHandlerRef which is defined in