Re: [Rest DSL] Automatic convertion of body to java.util.Map . How to fix it ?

It works! Using : Maybe adding the corresponding documentation for XML synthax to the documentation could be a good idea. I read the doc many time without understanding that this part also apply for XML. Anyway, thank you! Arthur. -- View this message in context:

Re: How to stop a route from processing get requests continously

I did this and it only brings me just one JSON from url, not how many elements I have in seda. How can I fix this? -- View this message in context: http://camel.465427.n5.nabble.com/How-to-stop-a-route-from-processing-get-requests-continously-tp5759649p5759690.html Sent from the Camel - Users

Bulk number of files consuming from a single file endpoint problem

Hi, I have files in a folder path to consume. When the number of files increase to more, around 5, some files moving to .error folder without processing and if will process the same file one by one it is processing and moving to .succes. Can you please help me to understand why it is

split big sql result in smaller chunks

Because of memory limitation i need to split a result from sql-component (ListMaplt;column,value) into smaller chunks (some thousand). I know about from(sql:...).split(body()).streaming().to(...) and i also know .split().tokenize(\n, 1000).streaming() but the latter is not working with

Re: split big sql result in smaller chunks

The jdbc component in 2.14 has a streaming list type. The sql component do not have that. For the split you can write a java bean method that returns an iterator, that iterates the list in chunks. Its actually what the tokenizer 1000 does. On Thu, Nov 27, 2014 at 11:51 AM, dermoritz

CxfBean Authentication

Hi, I'm using camel v2.12.3. I have a route running within JBoss EAP 6.1 like this (I'm not using spring configuration): from(jms:queue:test) .to(cxfbean:testServiceWS); The jms queue is located on another server and the message itself is providing some authentication information. The

Messages consumed from JmsComponent not marked as transacted

Hi, I am using Camel 2.10.4 (long overdue for an upgrade ;) ) I have configured a JmsComponent in xml to be transacted. However, when I run the unit test below, the exchanges are marked as *not* being transacted. If I add .transacted() to the java routing code, then exchange.isTransacted()

NPE with language:ruby and concurrentConsumers

Hi, after moving from Camel 2.8 to 2.14 I am facing a problem with the language component and ruby scripts. With concurrentConsumer 1, a NPE is thrown by the RubyInstanceConfig class: java.lang.NullPointerException at org.jruby.RubyInstanceConfig.init(RubyInstanceConfig.java:1432)

camel xslt with saxon 8.7

Hallo camel community, I just upgraded from camel 2.13.2 to 2.14.0. Camel git commit 1b38aad342529e98b5f76e11029ec50b1768949f (CAMEL-7753: xslt component - Store warning/errors etc as exchange properties so end users can get hold of those. Now works with camel-saxon also.) of 27-aug-2014

Re: PGP decryption cannot decrypt gzip file

Hello Shail, can you please provide the stack trace of the exception and the exact exception message. Regards Franz On Fri, Nov 21, 2014 at 8:45 PM, Shail shailendra.it...@boku.com wrote: Hi, I'm using camel ver 2.14.0. I'm successfully able to decrypt a file using pgp() function when I

Re: PGP Decryption Out of Memory for large file

Hello Shail, please try camel stream caching. See http://camel.apache.org/stream-caching.html Regards Franz On Fri, Nov 21, 2014 at 8:28 PM, Shail shailendra.it...@boku.com wrote: Hi, I'm using camel ver 2.14.0 in our application. We download the file from sftp server and then process it.

Somewhat inconsistent behaviour for message logging

Hi, I have looked into the coding for the logging of the payload in different locations of the Camel coding, but it looks somewhat inconsistent to me. In several places MessageHelper.extractBodyForLogging(Message) or MessageHelper.extractBodyForLogging(Message, String) is used to get a payload

Re: camel xslt with saxon 8.7

You may consider to use Camel 2.13.3 instead of Camel 2.14.0. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On November 27, 2014 at 9:12:48 PM, Ronny Aerts

Re: CxfRs producer: connection not closed

Thanks, I looked at your fix, seems prefectly fine for my usage. I have one question however: Should'nt you close the connection also when responseClass is provided ? (whatever the exchange pattern) I would think that response/connection should be left open only when we are able to consume (and

RE: camel xslt with saxon 8.7

Hallo Willem, Camel 2.13.3 is indeed an option but eventually I still want to follow the latest camel versions. So using an 'older' version is only a workaround for now. I want to use the sql component with the simple language to and therefore I need 2.14.0. -- Kind regards, Ronny Aerts –

Re: split big sql result in smaller chunks

I think stream list is on the jdbc driver level. And when using it you dont need any custom splitter code, just split on the body. On Thu, Nov 27, 2014 at 1:03 PM, dermoritz tantea...@hotmail.com wrote: Thanks for quick reply, but what is the difference between sql-component's

Error when using xquery

Hi Guys, I'm trying to do a transformation and using xquery for that. But apparently i'm getting Caused by: java.lang.IllegalArgumentException: No script engine could be created for: xquery at org.apache.camel.builder.script.ScriptBuilder.createScriptEngine(ScriptBuilder.java:287)

Re: split big sql result in smaller chunks

Thanks, with a normal split i have one row per exchange. So i would need an aggregator to create bigger chunks. But what is the difference to sql-components useIterator=true with this i also get one exchange per row but with no need to split. -- View this message in context:

Re: CxfRs producer: connection not closed

I think CXF WebClient already take care of it, the response is input stream,   the user should close it himself. In camel-http, the http client auto close the connection when it out of scope, so we have to copy the stream in camel for the outside usage. But it’s the user responsibility to close

RE: camel xslt with saxon 8.7

I’m afraid we cannot provide a wider rang of third party library support in Apache Camel. In this case, you may consider to back port the simple language patch to the Camel 2.13.x yourself, or you can just build the camel-saxon 2.13.3 with camel-core 2.14.0. -- Willem Jiang Red Hat, Inc.

Re: NPE with language:ruby and concurrentConsumers

Which version of JRuby are you using? I just ran the test in Camel master (2.15-SNAPSHOT) with JDK8 and JDK7, all tests are passed. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang

Re: NPE with language:ruby and concurrentConsumers

It’s look like an issue of JRuby, I reproduced the issue with JRuby 1.7.13, and the test was passed with JRuby 1.7.16. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem

Re: Error when using xquery

What’s your camel look like? You don’t need to use ScriptBuilder when using the xquery. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On November 27, 2014 at

Re: Somewhat inconsistent behaviour for message logging

We introduce a ExchangeFormatterRef option to RedeliveryErrorHandler[1] since Camel 2.15.0, it should be more easy for us setup ExchangeFormatter for the ErrorHandler. But It could more easy for us to manage the max chars option by set up the properties through the camel context. Please feel

Re: Servlet component matchOnUriPrefix is not working as documented

Can you try your test case with the latest released Camel 2.14.0 to see if the issue is still there? -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On November

Re: general approach to streaming

Tim, the SEDA component is designed to produce/consume messages quickly and provides a queue (BlockingQueue) in between resources to buffer the flow and provides options such as max size and blockWhenFull to limit memory usage and slow a producer as needed, etc... http://camel.apache.org/seda.htm

Re: Sending a Request to camel rout from rx java observable

That’s part of UnitOfWorkProducer job which means we get the response there. As not all the camel endpoints implement the async invocation API, we cannot use the async invocation by default. If the endpoint support the async invocation, you can call the producer async API yourself without using

RE: Somewhat inconsistent behaviour for message logging

Hi Willem, I was aware of the ExchangeFormatterRef option. With that it is possible to set that Option on the default error handler, but just in order to set the maximum number of characters it seems like a bit of overkill to me. I would propose the following order: 1. If the maxChars

RE: Somewhat inconsistent behaviour for message logging

It is consistent behaviour to let DefaultExchangeFormatter take the consideration of Exchange.LOG_DEBUG_BODY_MAX_CHARS property. +1 for your proposer. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese)

Camel

Hi, I want read below file in camel, ?xml version=1.0 encoding=utf-8? xs:schema elementFormDefault=qualified xmlns:xs=http://www.w3.org/2001/XMLSchema; xs:element name=Address xs:complexType xs:sequence xs:element name=Recipient type=xs:string / xs:element name=House

Re: CxfBean Authentication

You can set up the Authentication Properties dynamically just like this         MapString, Object requestContext = new HashMapString, Object();         requestContext.put(BindingProvider.USERNAME_PROPERTY, username);         requestContext.put(BindingProvider.PASSWORD_PROPERTY, password);