hi,
I'm using camel-sqs component, and I need to SET message attributes
when sending messages to SQS.
I tried:
process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Message in = exchange.getIn();
Map msgAttrs = new HashMap();
If you are working with queues you could send back to the message to the
first destination who will be your queue (or a failure/ dead-letter
queue) and process it again using an errorHandler for example.
On 4/02/2015 17:10, dbougie wrote:
I am trying to achieve an all or nothing, roll back all
Thank You, Will try this option.
On Wed, Feb 4, 2015 at 12:52 PM, Morgan Hautman
wrote:
> Mezai,
>
> Why don't you persist the last number you processed and put in a
> PropertyPlaceholder when polling again?
>
> http://camel.apache.org/using-propertyplaceholder.html
>
> Little example I made:
>
Hi
Have you asked the restlet guys if there is some issue in restlet itself?
If you think that method should return an array or something?
Its a bit hard to follow what you see as the problem in Camel / Restlet
On Mon, Feb 2, 2015 at 8:28 PM, sandp wrote:
> I came across a situation where the c
Hi
Yeah sure we love contributions
http://camel.apache.org/contributing.html
On Tue, Feb 3, 2015 at 10:42 PM, jechavez wrote:
> Hi Camel Community,
>
> I am seeing the following issue with the camel-quickfix component. I am
> sending a response FIX message back to a session defined in my quickfi
I am trying to achieve an all or nothing, roll back all on exception when
using multicast. I have stopOnException enabled. My understanding however is
that this will just stop the continuing of processing/sending messages. If
the first delivery succeeded and the second failed then multicast would n
thank you, I'll take a look into it
--
View this message in context:
http://camel.465427.n5.nabble.com/Exposing-request-response-Web-Service-that-would-interact-with-legacy-system-tp5762229p5762392.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
thank you for your response. I see an issue that legacy API is "JMS like",
not really supporting things like replyTo headers, or queues whatsoever
among other things.
It's more about communication type - request goes one way, and then
asynchronously response comes from another place. I am a bi
Have you look into the Camel Aggregator pattern?
http://camel.apache.org/aggregator.html
If you have any mechanism in the request/response message to correlate a
request to a response, you can set up the aggregator to collect your
response from a separate route and match the request/response usin
Great, It looks it working fine
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-SFTP-Zero-size-file-download-tp5762381p5762385.html
Sent from the Camel - Users mailing list archive at Nabble.com.
The URI is just a string.
Why not extract your "builder" into a simple utility method
public class EndpointUtils {
public static String rabbitEndpoint(String scheme, String host, String
host) {
...
}
}
With SpringDSL property placeholder come into mind ...
Having special builde
Is there a standard pattern for defining Camel endpoints so that
commonly used endpoint settings do not need to be repeated in every
endpoint definition? For example, every RabbitMQ endpoint I declare
always repeats the same connection settings like the following:
rabbitmq://{{rabbitmq.host}}
Hi
You can try different read locks, such as changed which is supported by ftp.
Another alternative is if the "writer" writes the file using a
temporary name and then rename when its done, or write to some other
directory first, and then move the file in the end. Or write a 2nd
"done" file etc.
I am downloading PDF file from server using camel SFTP component. Sometime
it is downloading zero size file. but actual size is 4kb. I think camel is
downloading the file while it is being written. kindly let me know how to
download the file after file written operation is done. Give some example.
Thanks again Bart
I was trying the solution you proposed, only challange is reading email
from INBOX and placing on a JMS queue was taking around 6-7 seconds.
I have implemented a route to distribute emails to multiple folders from
INBOX and created multiple listeners on these folders.
-Thanks
Sas
In the docs you could find a number of possibilities:
http://camel.apache.org/clustering-and-loadbalancing.html
A solution could be to poll the mailbox and then put the messages on a jms
queue and then poll them of the queue with concurrent consumers.
This allows you to do the processing over dif
16 matches
Mail list logo