Re: Multicast not to route messages

> > May be a Recipient List is what you need: > http://camel.apache.org/recipient-list.htm > I agree, with the recipient list you will be able to do multicast in a dynamic fashion and have your implementation decide which will be the destinations at any

Re: Multicast not to route messages

Hi Narita, May be a Recipient List is what you need: http://camel.apache.org/recipient-list.html Regards, Ngoc Hai --- On Thu, 9/22/11, Narita Bagchi wrote: > From: Narita Bagchi > Subject: Multicast not to route messages > To: "users@camel.apache.org" > Date: Thursday, September 22, 2011,

Re: SOAP Headers and spring-ws

On Thu, Sep 22, 2011 at 4:18 AM, Damian Harvey wrote: > We have a small issue with the way that the SpringWebserviceConsumer > retrieves SOAP Headers. > > SOAP Headers must be namespace qualified > (http://www.w3schools.com/soap/soap_header.asp), and when the Consumer > extracts the SOAP header

Multicast not to route messages

Is there a way to inform "Multicast" not to route messages to some routes, at a given point in time? Why this is needed - Multicast routes messages to multiple destination. While processing/routing, few messages reached the intended destination and few did not(say, due to crash). Recovery runs

Re: Message.copy() not exactly a copy

On Thu, Sep 22, 2011 at 2:51 AM, samslara wrote: > Hi, >  I currently have a camel route that makes use of HttpComponent.  After > calling a service and getting a String back in the body I tried to do a > Message.copy(), with the Message being from exchange.getIn().  The original > Message body is

SOAP Headers and spring-ws

We have a small issue with the way that the SpringWebserviceConsumer retrieves SOAP Headers. SOAP Headers must be namespace qualified (http://www.w3schools.com/soap/soap_header.asp), and when the Consumer extracts the SOAP headers to populate the Exchange Headers it uses the QName.toString() m

endpoint URI can't parsed failed use utf-8?

[java] Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: sunlink:/ 0.0.0.0:5090?backLog=100&fileDir=runtime%2Ffiles&localNode=999&logDir=runtime%2Flogs&poolQueueDepth=10&poolSi e=20&remoteNode=000&version=2 due to: Invalid byte 1 of 1-byte UTF-8 sequence.

Re: why my Processor throw Exception but producer can't throw it

I suggest you to use the RouteBuilder to define the route with Java DSL. It's the normal way that we do it, On Tue Sep 20 21:18:50 2011, xiangqiuzhao wrote: camelContext.addRouteDefinition(someRouteDefinition); i look the camelContext and routeDefinition had exception handler, i has no set exc

Re: Newbie: how to test?

When you are planing to test your route as an unit test, you can register a seda component with the name for jms. Then you can fire the message to the seda endpoint. There are lot of other way to do it in Camel in Action Charpter6, you need to have a one :) On 9/21/11 7:07 PM, kenhans wrote:

Message.copy() not exactly a copy

Hi, I currently have a camel route that makes use of HttpComponent. After calling a service and getting a String back in the body I tried to do a Message.copy(), with the Message being from exchange.getIn(). The original Message body is of type String but the new Message body isn't of type Stri

Re: Global exception not invoked in case of Exception fired while iterating through File Splitter

Hi, Now i have tried with version 2.9.0-SNAPSHOT also but it's still not working. What's the solution/workaround? Regards, Nilesh Soni -- View this message in context: http://camel.465427.n5.nabble.com/Global-exception-not-invoked-in-case-of-Exception-fired-while-iterating-through-File-Splitter-

Re: Global exception not invoked in case of Exception fired while iterating through File Splitter

I am using version 2.8.0 and i have also tested the code with version 2.8.1. When 2.9.0 is scheduled to be released? -- View this message in context: http://camel.465427.n5.nabble.com/Global-exception-not-invoked-in-case-of-Exception-fired-while-iterating-through-File-Splitter-tp4826097p4827013.h

Re: HazelcastComponentHelper copyHeaders issue

Created CAMEL-4472 -- View this message in context: http://camel.465427.n5.nabble.com/HazelcastComponentHelper-copyHeaders-issue-tp4825799p4826111.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Global exception not invoked in case of Exception fired while iterating through File Splitter

Hi What version of Camel are you using? I think we have fixed this in either 2.9 or one of the latest releases. On Wed, Sep 21, 2011 at 2:04 PM, nilsoni wrote: > Hi All, > I have written a file route which picks up xml files from a specified > location. This file is passed to a splitter (actua

Global exception not invoked in case of Exception fired while iterating through File Splitter

Hi All, I have written a file route which picks up xml files from a specified location. This file is passed to a splitter (actually an Expression written by me) which returns a custom made Iterator and returns to Camel. When camel is iterating through my iterator, if I throw RuntimeException, it is

Re: package org.apache.camel.core.xml is not exported (OSGi) - using Camel 2.7.3

me too :-) your hint was very helpful, it solved my current problem and knowing about fragments will be useful for me beyond that for sure. Really glad, this works for you

Re: Newbie: how to test?

The easy way is to look at: http://camel.apache.org/camel-test.html The harder way is a deeper conversation as there are several tricks in testing routes and Camel. Start small with the above link then you will have better questions as you go along. Also, sorry for the plug, but this book is the

Newbie: how to test?

hello, I started looking into Camel a few days ago and was wondering how to test... I define my camelContext through Spring, with the route I want to use http://camel.apache.org/schema/spring";> my subscriptionRoute is defined like this: from("jms:queue:subscription"). where jms is

Re: HazelcastComponentHelper copyHeaders issue

Hi Thanks for reporting. Do you mind creating a JIRA ticket for this bug? There is a link to JIRA from here http://camel.apache.org/support And as we love contributions, you are welcome to work on a patch as well. On Wed, Sep 21, 2011 at 11:48 AM, Tomislav Mrkus wrote: > Hi, > > due to lazy c

HazelcastComponentHelper copyHeaders issue

Hi, due to lazy creation of Out message in DefaultExchange.getOut() implementation, HazelcastComponentHelper.copyHeaders() method inadvertently creates an Out message if one has not been set yet, which then creates problems in CamelInvocationHandler.getBody() which then returns null as a result.

Re: Transaction Error Handler with Dead Letter Channel

On Wed, Sep 21, 2011 at 10:48 AM, jason.parr wrote: > Is this still the case that there is no way to specify a dead letter channel > if you want to use a JTA/XA transaction spanning JMS & JDBC operations etc. > > If you many applications and all transactional failures get routed to the > same spot

Re: Transaction Error Handler with Dead Letter Channel

Is this still the case that there is no way to specify a dead letter channel if you want to use a JTA/XA transaction spanning JMS & JDBC operations etc. If you many applications and all transactional failures get routed to the same spot, eg for activemq goto ActiveMQ.DLQ this would be unacceptable

Re: package org.apache.camel.core.xml is not exported (OSGi) - using Camel 2.7.3

> > Thanks Ioannis, Willem. > > Deploying a few JAXB related classes/resources of my extension as a > fragment attached to org.apache.camel.camel-spring was the way to go. > Really glad, this works for you! -- *Ioannis Canellos* * FuseSource ** Blog: http://iocanel.blog

Re: package org.apache.camel.core.xml is not exported (OSGi) - using Camel 2.7.3

Thanks Ioannis, Willem. Deploying a few JAXB related classes/resources of my extension as a fragment attached to org.apache.camel.camel-spring was the way to go. Regards, Stefan You can find the classes in the camel-spring or camel-blueprint. When your bundle is attached to the camel-spring

Re: SMPP Bind timeout

> > It's better to ask the Huawei guys... ;-) > >From my personal experience with people working on SMSCs (I've been doing this for years) its faster and more reliable to trace the issue yourself. They are usually up to the neck with tasks ... -- *Ioannis Canellos* * FuseSource