Re: need create a route which can handle several encoding

melCharsetName") and value that > you want. > > You can do it with DSL > > setProperty(Exchange.CHARSET_NAME, > ExpressionBuilder.constantExpression("UTF-8")) > > or Spring config > > UTF-8 > > > Willem > > > > mcrive

need create a route which can handle several encoding

Hi, my route gets a feed (string) from a web service and distribute it to several endpoint. when I get the feed I might get it in UTF-8 or ISO-8859-I and I would like to respect this encoding when distributing the feed to the endpoint(s). The feed is stored as body of the exchange. At the moment

Re: mail component, subject as an option?

: >> >>> Hi >>> >>> I have created the ticket >>> https://issues.apache.org/activemq/browse/CAMEL-2467 >>> >>> On Fri, Feb 12, 2010 at 3:01 PM, Claus Ibsen >>> wrote: >>>> On Fri, Feb 12, 2010 at 2:54 PM, mcrive >>&g

Re: mail component, subject as an option?

Is attaching the patch a must have? :) Claus Ibsen-2 wrote: > > On Fri, Feb 12, 2010 at 2:42 PM, mcrive wrote: >> >> I think it would be very useful having an option to specify the subject >> of >> the email in the mail component URI. >> This would

mail component, subject as an option?

I think it would be very useful having an option to specify the subject of the email in the mail component URI. This would be very convenient especially using recipientList component :) If needed I can open a ticket for it Regards, Marco -- View this message in context: http://old.nabble.com/m

Re: GenericFileProducer behavior when temp file is used

I' ve opened a ticket for it https://issues.apache.org/activemq/browse/CAMEL-2466 I will try to produce a patch as well but I don't have a very big experience in Java... where should I post it? Claus Ibsen-2 wrote: > > On Thu, Feb 11, 2010 at 6:00 PM, mcrive wrote: >>

Re: GenericFileProducer behavior when temp file is used

y you perform file upload is not safe. Regards, Marco Claus Ibsen-2 wrote: > > On Wed, Feb 10, 2010 at 5:17 PM, mcrive wrote: >> >> Hi, >> looking into the source code of GenericFileProducer I found out that when >> using the tempFileName option following happens: &

Re: recipientList retryUntil not working?

> > Then update your code to set up a right Registry. > > Willem > > mcrive wrote: >> what if I am not using CamelTestSupport? >> >> Stephen Gargan wrote: >>> If you're using CamelTestSupport you can do the following... >>> >>>

Re: recipientList retryUntil not working?

jndi.bind("myRetryBean", "somebean"); > System.err.println(jndi.lookup("myRetryBean")); > return jndi; > } > > On Wed, Feb 10, 2010 at 10:23 AM, mcrive > wrote: >> >> Hi, >> I have built current trunk >>

Re: recipientList retryUntil not working?

moment I am doing this: JndiRegistry jndi = new JndiRegistry(new JndiContext()); jndi.bind("myRetryBean", new RetryBean()); looking into the unit tests I can't find any sample... Claus Ibsen-2 wrote: > > On Thu, Feb 4, 2010 at 9:34 AM, mcrive wrote: >> >>

GenericFileProducer behavior when temp file is used

Hi, looking into the source code of GenericFileProducer I found out that when using the tempFileName option following happens: - if final file exists it gets deleted - temp file gets written - temp file gets renamed into final file Deleting the final file before uploading the new file seems unsa

Re: file language question

so it is supposed to work in such a way Claus Ibsen-2 wrote: > > On Wed, Feb 10, 2010 at 3:50 PM, mcrive wrote: >> >> Hi, >> I have a question about file language >> >> say I have following endpoint >> >> ftp://u...@host?password=pwd&

file language question

Hi, I have a question about file language say I have following endpoint ftp://u...@host?password=pwd&fileName=foldername/filename.extension&tempFileName=${file:name.noext}.tmp the temp file name which will be used is: foldername/filename.tmp if I change tempFileName to tempFileName=${file:only

Wrong trace on GenericFileProducer?

Hi, debugging an issue I am facing sending an exchange to an FTP endpoint I found a possible wrong trace statement on the GenericFileProducer @line 104 (current trunk) if (log.isTraceEnabled()) { log.trace("Deleting existing file: " + tempTarge

Re: recipientList + AggregationStrategy

Hi Claus, I saw trunk is for 2.3 now, do you have a plan about when you will check in the patch? https://issues.apache.org/activemq/browse/CAMEL-2429 Claus Ibsen-2 wrote: > > After the 2.2 release which is happening soon. I think Hadrian will > start to build the 2.2 release early this week. >

Re: recipientList retryUntil not working?

is building current trunk another option? Claus Ibsen-2 wrote: > > On Wed, Feb 3, 2010 at 2:40 PM, mcrive wrote: >> >> >> >> mcrive wrote: >>> >>> I've tried both things you suggested but it is still not working, the >>> retry h

Re: recipientList retryUntil not working?

mcrive wrote: > > I've tried both things you suggested but it is still not working, the > retry happens in default manner. > > I've opened a ticket in JIRA: > https://issues.apache.org/activemq/browse/CAMEL-2360 > > were you able to replicate the issue

Re: recipientList + AggregationStrategy

Wonderful news! thanks a lot Camel rocks! Claus Ibsen-2 wrote: > > After the 2.2 release which is happening soon. I think Hadrian will > start to build the 2.2 release early this week. > -- View this message in context: http://old.nabble.com/recipientList-%2B-AggregationStrategy-tp27305176p

Re: recipientList + AggregationStrategy

Hi, I saw you attached a patch to the ticket which will go to Camel 2.3, is there a plan on when you will start developing 2.3? Thanks again, Marco Claus Ibsen-2 wrote: > > > I have created a new ticket as I think it can make Camel better > https://issues.apache.org/activemq/browse/CAMEL-2429

Re: recipientList + AggregationStrategy

uch as endpoint and time > taken etc. > > Then you could just register a notification listener and grab that > stats as they come flying in. > > > > > > >> >> mcrive wrote: >>> >>> If you need to have people creating such a sam

Re: recipientList + AggregationStrategy

Hi Claus, having a way to retrieve transfer time to an endpoint (FTP mostly) is key feature of the application I am writing (as a part of a bigger software system). You told me I should consider consultancy, can you give me any direction? Who should I contact? mcrive wrote: > > If you n

Re: recipientList + AggregationStrategy

if I put a destination after the recipientList its gets processed once all endpoints got processed that means I can't compute transfer time of a single endpoint. I can't understand why you would use the interceptor, the interceptor isn't called when the message has been delivered to the endpoint

Re: recipientList + AggregationStrategy

Hi Claus, I am sorry but I don't understand what you mean... would it be possible for you to send me a sample (just the route) Claus Ibsen-2 wrote: > > Hi > > Interesting use case you got. > I got to go over this again at another time. I am at a business > convention in the US which means I a

recipientList + AggregationStrategy

Hi, I am using recipientList to send a message to a list of endpoints (mostly FTP). I am using an AggregationStrategy to compute few properties of the exchanges: - delivered - how many retries - time taken I've been able to get 'delivered' and 'how many retries' for each endpoint but I can't fin

Re: recipientList retryUntil not working?

I've tried both things you suggested but it is still not working, the retry happens in default manner. I've opened a ticket in JIRA: https://issues.apache.org/activemq/browse/CAMEL-2360 Claus Ibsen-2 wrote: > > Hi > > Can you try moving the onException on up? > > And if still a problem then

recipientList retryUntil not working?

I have following route: from("jms-test:queue:queue.delivery.notification.test") .process(processor) .onException(Exception.class).retryUntil(bean("myRetryBean")).end() .recipientList(header("recipientListHeader").tokenize(",")) .parallelProcessing().e

Re: recipientList redelivery

I think there is a small in the documentation In Errors Handlers features it is listed "redeliverUntil" http://camel.apache.org/error-handler.html while the feature seems to be named "retryUntil" http://camel.apache.org/exception-clause.html Claus Ibsen-2 wrote: > > No you should not. Use the

Re: recipientList redelivery

Claus Ibsen-2 wrote: > > You can use redeliverUntil to determine whether or not redelivery should > occur. > > And you can get the failed endpoint as a property: > String failedEndpointUri = > exchange.getProperty(Exchange.FAILURE_ENDPOINT, String.class); > > Then in your redeliverUntil you ca

recipientList redelivery

hi I am using Camel 2.2, is there a way to specify a different value of maximumRedeliveries for each endpoint when using recipentList? -- View this message in context: http://old.nabble.com/recipientList-redelivery-tp27143430p27143430.html Sent from the Camel - Users mailing list archive at Na

Re: recipientList + aggregationStrategy, maximumRedeliveries exceeded

even without indicating that I am handling the exception it doesn't reach the aggregationStrategy from("jms-test:queue:queue.delivery.notification.test").process(processor) .onException(Exception.class).maximumRedeliveries(2).redeliverDelay(60L).end() .recipientList(header("recipientListHeader").

Re: recipientList + aggregationStrategy, maximumRedeliveries exceeded

when the exchange hits the aggregationStrategy the header is no longer set. Claus Ibsen-2 wrote: > > > See section - Redelivery header > http://camel.apache.org/dead-letter-channel.html > > These headers apply also for the default error handler in Camel 2.x. > -- View this message in cont

recipientList + aggregationStrategy, maximumRedeliveries exceeded

I am using Camel 2.2 (rev 890454) How is it possible to know if an exchange has exceeded the maximumRedeliveries configured on the route by using aggregationStrategy and if it hasn't how many redelivery have been attempted? route sample: from("direct:delivery.notification.test") .onException(Ex

Re: recipientList onException redelivery

I've just a little but of testing and it looks like it works fine.:clap: I'll develop an application on top of recipientList so I'll let you know if I find new issues with regard to this matter. thanks for the fix!! camel is my best friend :drunk: mcrive wrote: > >

Re: recipientList onException redelivery

Claus Ibsen-2 wrote: > > I have worked on this and committed a fix. Can you test it on your end? > Hi Claus, sorry for the late reply but I just came to the office (I am traveling a lot) I am currently compiling latest revision and will test it soon. Thanks, Marco -- View this message in co

recipientList onException redelivery

Hi, i am using recipientList with the cool parallelProcessing feature added on camel 2.2. it works like a charm. the recipientList contains a csv list of ftp endpoints. I would like to retry the delivery in case it fails. I've set up an onException with maximumRedeliveries set to 2. Problem is in

Re: recipientList multithreading

Hi, I would really enjoy trying the 2.2 (I was already working with 2.1 SNAPSHOT) I can't find a zip with the libraries, do I have to compile it by my own? Is there a roadmap for the 2.2 release? Do you have a date in which you would release it? Thank you! Claus Ibsen-2 wrote: > > > Hi > > I

Re: recipientList multithreading

Nice one. Can you suggest a way to achieve what I need to do with Camel 2.1? Claus Ibsen-2 wrote: > > No but we got a ticket for it > https://issues.apache.org/activemq/browse/CAMEL-2223 > > And its possible to implement as the underlying logic supports it - so > its merely just to expose the

recipientList multithreading

Is there a way to make the recipientList to send to endpoint in a multi thread manner? for instance if it contains a list of FTP endpoint (producer) I would like to deploy files at the same time. as it is implemented now it starts producing the 2nd as the 1st is completed -- View this message in

Re: Camel 2.1 FTP Component issue with tempPrefix or tempFileName

created: https://issues.apache.org/activemq/browse/CAMEL-2153 Claus Ibsen-2 wrote: > > Hi > > Could you create a ticket in JIRA. > > And also pin point exactly which file is that you mean when you say > "when the destination file exists". > - is it the temp file > - is it the final destinatio

Camel 2.1 FTP Component issue with tempPrefix or tempFileName

Hi, I am using FTP component to push files via FTP. I am facing issues pushing a file on subfolder when using tempPrefix or tempFileName. route sample: from("direct:start").to("ftp://usern...@ipaddress?password=mypass&fileName=./camel/test/message.txt&tempFileName=${file:name.noext}.tmp";); no

Re: Error handling with recipientList

Ok, many thanks for the precious help Claus Ibsen-2 wrote: > > And if you are looking for such kind of support you very likely have > to acquired paid support. Which offers such kind of custom specific > patches. > -- View this message in context: http://old.nabble.com/Error-handling-with-r

Re: Error handling with recipientList

Isn't the trunk where you commit the one containing changes after 2.0 REL? I am facing the issue with 2.0, everything is fine with 2.1. Claus Ibsen-2 wrote: > > On Thu, Nov 5, 2009 at 4:09 PM, mcrive wrote: >> >> doing the same thing with Camel 2.1 I can see what I a

Re: Error handling with recipientList

exchange.getProperty(Exchange.EXCEPTION_CAUGHT, Throwable.class); Message inMsg = exchange.getIn(); //inMsg body is the original one and not the one that has been modified by the interceptor. } Claus Ibsen-2 wrote: > > On Wed, Nov 4, 2009 at 5:12 PM, mcrive wrote: >&

Re: Error handling with recipientList

I've configured following route: interceptSendToEndpoint("*").process(new SendToEndPointHandler()); onException(GenericFileOperationFailedException.class) .process(new DeliveryFailureHandler());

Re: Error handling with recipientList

thank you for such a quick reply! I am currently using 2.0 REL, is there a way to do the same thing with the version I have? Claus Ibsen-2 wrote: > > On Wed, Nov 4, 2009 at 2:40 PM, mcrive wrote: >> >> I ha following route >> >> >> onException(Gener

Error handling with recipientList

I ha following route onException(GenericFileOperationFailedException.class) .process(new DeliveryFailureHandler()).stop(); from("test-jms:queue:feed.notificationtest.queue") .process(processor)