Re:

Rick, what makes you think that the camel-salesforce or any other component "hijacks" headers? If you set a header - that is not used by this component - it should leave it untouched at the message. However, if this is working there is no reason to have a stateful service thus avoiding issues wit

Re: Exchange Body is null while using processor

Hi Claus, If we do it like this, we can get the POST values into process Exchange. from("servlet:///hello?servletName=TestServlet").streamCaching().log("log: ${body}").process(new Processor() { public void process(Exchange exchange) throws Exception {

Re: Invoking Camel restlet producer giving an exception

Yeah Claus...but even after adding that header am getting the same exception. Am i going in the right direction ? -- View this message in context: http://camel.465427.n5.nabble.com/Invoking-Camel-restlet-producer-giving-an-exception-tp5754603p5754616.html Sent from the Camel - Users mailing lis

RE:

Hiya, Yeah, but I think that assumes that components will be thoughtful enough to pass me what I want back. If a component (e.g. camel-salesforce) needs both the header and body for me to make a request-response, I have to hope that it passes me the service bean instance (that's also in the ex

Re:

Spring-Web has the notion of a "request-scope", which binds the lifetime of the instance to a Thread. That's likely what you want. As soon as you spin-off a new Thread within you route (using async components, like seda, jms or similiar) Spring would create a new instance. However, not sure if thi

RE: TokenizeXML by value from message header

As of now tokenizer does not evaluate properties/expression, so you have to pass string value. I am curious to know if one can refer/access current exchange object while defining the route. If that is possible then something like this will work in your case. from("direct:start").split().tokeni

Re:

Maybe create an instance and stick it into a camel header (the header will follow the exchange, and thus the lifecycle of passing through the route).? 2014-07-29 22:10 GMT+02:00 rickaroni : > Hi Michael, > > I hear you. The trouble is, sometimes the intermediate transports (e.g. > the > Camel S

Re: Load Testing Camel Routes

Hi Matt! We are using httpcore-ab [1] to load test our web services. Unfortunately, you cannot change the payload for each test, but it works well for us. [1] http://search.maven.org/#artifactdetails|org.apache.httpcomponents|httpcore-ab|4.3.2|jar Best, Christian - Software Int

Camel-Restlet 2.13.1 working for invalid URL ( valid URL+some junk)

Camel-Restlet is responding with valid response to any junk (text) appended to the actual URL. *Actual URL:http://localhost:8090/cts-rest/cts/users* If I add something to the Actual URL like *http://localhost:8090/cts-rest/cts/users+junk(*/*)*, I see a valid response that is only supposed to be

Re:

Hi Michael, I hear you. The trouble is, sometimes the intermediate transports (e.g. the Camel Salesforce component) hijack the header and body for their own needs and you don't have full control over them. In similar ESBs, I've seen some shops make their own custom Spring message scope to be the

Load Testing Camel Routes

Hello all, I'm getting ready to put a Camel / CXF / Spring Boot application into production. Before I do, I want to load test and verify it has the same throughput as a the IBM Message Broker system it's replacing. Apparently, the old system can only do 6 concurrent connections because of remot

Re:

Hi Rickaroni, from my point of view, I always find it a little disturbing having state in my services, because from a certain point it makes things complicated. To quote the Spring docs: "The non-singleton, prototype scope of bean deployment results in the creation of a new bean instance every ti

Re: Invoking Camel restlet producer giving an exception

Hi Rest services usually requires and use the Accept header exchange.getIn().setHeader("Accept", "application/xml"); On Tue, Jul 29, 2014 at 6:34 PM, Raju Mandala wrote: > Hi, > > I am working on a sample application to invoke a RESTful web service using > camel routing. And the REST service is

Re: Is there parameters missing when using topic/ selector ?

Thanks i will try something like this tomorrow on the job. from("file:c:/camel-input/?delete=true") .setHeader("BD", "YES") to("activemq:queue:BCA_TEST"); -- View this message in context: http://camel.465427.n5.nabble.com/Is-there-parameters-missing-when-using-topic-selector-tp5754574p575460

Invoking Camel restlet producer giving an exception

Hi, I am working on a sample application to invoke a RESTful web service using camel routing. And the REST service is secured. I coded like this from("file:data/source?noop=true") .process(new Processor() { @Override

Re: Is there parameters missing when using topic/ selector ?

If you're producing to a topic or queue, you need to set headers (aka JMS properties) in order to use them in a selector on the consumer side. On 29 July 2014 06:31, Frankiboy wrote: > Okay let me know if i undertand this correct i new to MQ ? > > I have a topic named: > > "HUB_TOP01" > > There

users@camel.apache.org

Hi Claus et al, I'd like to use a prototype bean in a route such that a new instance gets created at the beginning of the route, and that same instance is used throughout the route until the route ends. Included below are two simple routes and a fragment of a service bean class that collects part

Re: Discarding inflight messages on shutdown and unavailable JMS provider

Hi If you enable asyncRedelivery then the error handler should be able to shutdown quicker when you set allowRedeliveryWhileStopping = false On Tue, Jul 29, 2014 at 3:40 PM, matrogenius wrote: > Hello, > > We have a simple Camel route from vm:xxx to jms:topic:yyy. The number of > redelivery att

Discarding inflight messages on shutdown and unavailable JMS provider

Hello, We have a simple Camel route from vm:xxx to jms:topic:yyy. The number of redelivery attempts has been set to infinite in the default error handler, so if the JMS provider goes down for some reason, Camel will retry to deliver the currently processed message until the JMS provider is up aga

TokenizeXML by value from message header

Hi, I'm trying to tokenize (by grouping) a body of a message based on a values from message header. The value from message header differs from one message to another. But it is not working. Is this not supported by camel? or should be done in a specific way? I've tried different ways. ( int grou

Re: Handle SOAP fault message

Can you elaborate how to handle the exception? If you just use producer template to send the request, you cannot leverage the camel error handler to handle the SOAP fault. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.

Re: Is there parameters missing when using topic/ selector ?

Okay let me know if i undertand this correct i new to MQ ? I have a topic named: "HUB_TOP01" There is three selectors: selector=BD= 'YES selector=BEC = 'YES selector=SDC = 'YES The selector is only for the subscriber and not the publischer. So away with the selctor, but what is correct

Re: Why RuntimeCamelException is thrown whenever some IOException occur for write/read

Hi, Actually, camel will wrap any of your exception or other exception in a RuntimeCamelException. You can handle exceptions (including wrapped exception) in many ways in camel (http://camel.apache.org/error-handling-in-camel.html) 2014-07-29 6:03 GMT+02:00 Satyam Singh : > Hello, > > > I am u

Re: How to pass multiple custom objects to processor

Hi, As I don't know your data structure, it's difficult for me to give you a specific (or "best") way. But you have 2 possibilities (see http://camel.apache.org/aggregator.html) : 1. Use a custom aggregation strategy in java code 2. Use the option "grouped exchanges" or use a "custom aggreg

Re: How to pass multiple custom objects to processor

Thanks arnaudeprez. This sounds like that this could work. 1. Splitting - i understand , i can unmarshal header and body via xpath separately and i am good. Any specific way to collect these two objects and in collection ? And, if i manage to put my two objects in a collection, in what format

Re: Is there parameters missing when using topic/ selector ?

Hi The JMS selector is only for the consumer, eg in the from. Also mind that non durable topics will discard the message if there is no active consumers listening on the topic. If the topic is durable then the broker stores the message, so when consumers later connect they can get those messages

Re: How to pass multiple custom objects to processor

Thanks Matt. //MyXpath And the corresponding getter i.e exchange.getProperties().get("bodyPart") gives me null. Same with Result. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-pass-multiple-custom-objects-to-processor-tp5754502p57

Is there parameters missing when using topic/ selector ?

I got this route from("file:c:/camel-input/?delete=true").to("activemq:topic:HUB_TOP01?selector=BD='YES'"); When i put a file into the camel-input directory, the file is deleted, but nothing in the MQ. Should i use clientID or other options ? I have tryed this out: from("file:c:/came

Re: IBM MQ The data received from host is not valid ?

I find the problem, i missed one jar file com.mq.mq.jms.jar so this problem is solved -- View this message in context: http://camel.465427.n5.nabble.com/IBM-MQ-The-data-received-from-host-is-not-valid-tp5754448p5754573.html Sent from the Camel - Users mailing list archive at Nabble.com.

Unicode character issues - Incoming Russian Characters

Hi guys Am facing a different kind of problem this time. I have message coming in from a system in Russia. The message looks like below. I am applying XSLT transformation and the output is very different from the data I hav

Re: Handle SOAP fault message

Hi arnaudeprez, *This my CXF configuration*

Re: Handle SOAP fault message

Hi, Can you show us how you have configured your endpoint "TransactionBegin" and also the method signature of "begin". Normally, by using CXF/JAXWS, the SOAPFault message should mapped to an Exception. and in your code you must handle this exception. If it's not the case, CXF won't be able to map

Re: Handle SOAP fault message

Hi arnaudeprez, I'm not able to catch in catch block of code. I dont know how to implement with other two methods. *Here is my code* private void invokeTransactionBegin(Exchange exchange) { if (exchange == null) { return;

Re: Handle SOAP fault message

Hi Jaishankar, Actually, Camel will not throw a SOAPFaultException, but a CamelRuntimeException that wraps a SOAPFaultException. Instead of handling exception by hand, Camel can do it for you in 3 different ways depending on what you'd like to do : 1. http://camel.apache.org/dead-letter-chann

Re: Failed to start route route2 because of Multiple consumers for the same endpoint is not allowed

Ahhh thats the way to do it , Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Failed-to-start-route-route2-because-of-Multiple-consumers-for-the-same-endpoint-is-not-allowed-tp5754511p5754558.html Sent from the Camel - Users mailing list archive at Nabble.com.