On 06/02/15 02:14, Claus Ibsen wrote:
On Wed, Feb 4, 2015 at 11:17 AM, Jan Matèrne (jhm) wrote:
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
Hi all,
I have refactored a legacy Java application (i.e. no web container) to use
Camel to send messages from files to a queue. I chose to describe my routes in
XML so the routes could be re-used in a future Spring web application. My
legacy application loads the XML routes using
ModelCamel
With the below I can put a image in the mail body
Multipart multipart = new MimeMultipart();
BodyPart htmlPart = new MimeBodyPart();
htmlPart.setContent(content, "text/html; charset=UTF-8");
BodyPart imagePart = new MimeBodyPart();
DataSource fds = new FileDataSource(pathImage);
imagePart.setDat
I see this is fixed in 15.0. I can use the snapshot but how do I use this
feature?
By the way, this is my solution for IMO a shortcoming in Camel (after using
it for a year) - the inability to pass objects to consumers except via
essentially static beans or something like ehcache. I'm using addRou
Hi
Thanks for coming back and telling us the solution.
And also we now have an unit test for that functionality, so its only good.
On Thu, Feb 5, 2015 at 3:34 PM, A.Light wrote:
> Ok, at the end, I found what my problem was. I'm ashamed to admit, the
> problem was between the keyboard and the c
Ok, at the end, I found what my problem was. I'm ashamed to admit, the
problem was between the keyboard and the chair, thus me.
This are the gotchas:
- I created the folder "process" under inbox, but with the command
"copyTo=process" I'm actually referring to a folder at the root of the email
fold
On Wed, Feb 4, 2015 at 11:17 AM, Jan Matèrne (jhm) wrote:
> 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) {
> ...
> }
> }
>
>
Use an onException and the you can log the file name, such as
onException(Exception.class).log("Darn error processing file
${file:name} due ${exception.message}");
On Thu, Feb 5, 2015 at 12:38 PM, geppo wrote:
> Great! That works.
> Thank you very much.
>
> Any idea how to log the filename on er
I have a route:
from("direct:input")
.wiretap("direct:sendToTopic")
.to("mongodb:deliveredEventMongoDB?database=ngw&collection=deliveredevents&operation=insert");
direct:input provably receives a brand new BasicDBObject filled with a
document and lacks a _id.
direct:sendToTopic provably receives
Great! That works.
Thank you very much.
Any idea how to log the filename on error?
By default it just logs the ExchangeId, which is not very useful.
--
View this message in context:
http://camel.465427.n5.nabble.com/Idempotent-and-errorHandler-tp5762408p5762412.html
Sent from the Camel - Users
Hi
Can you try set removeOnFailure=false on the idempotent consumer
http://camel.apache.org/idempotent-consumer.html
On Thu, Feb 5, 2015 at 11:57 AM, geppo wrote:
> Hi, I have a route with a File idempotent repository and an errorHandler.
>
> When a specific file causes an error I want it to be
Hi, I have a route with a File idempotent repository and an errorHandler.
When a specific file causes an error I want it to be added to the idempotent
repository so it doesn't get processed again. Any idea how to do it?
With the code below, the corrupted file is not added to the idempotent
reposi
That's where I ended up too. I was minded to make onPrepare a fragment for
embedding into wiretap too however one might imagine that someone using
wiretap does not want to modify the exchange based on individual onward
paths.
So in our case multicast() may be more appropriate with stopOnException(
James,
It seems to be documented here: http://camel.apache.org/multicast.html
(end of page)
And the class they use:
https://github.com/apache/camel/blob/master/camel-core/src/test/java/org/apache/camel/processor/AnimalDeepClonePrepare.java
Regards,
Morgan
On 5/02/2015 10:38, James Green wrot
Hi James,
I found some tests about mailProducer here:
https://github.com/apache/camel/blob/master/components/camel-mail/src/test/java/org/apache/camel/component/mail/MailProducerTest.java
https://github.com/apache/camel/blob/master/components/camel-mail/src/test/java/org/apache/camel/component/
Yes this is the simple bit.
The not so simple bit is appreciating what happens under the hood. wiretap,
quite rightly, sends the same object references down each path. If one of
those paths mutates the Exchange's Message, the other routes will spot the
change and the developer gets a rude surprise
http://camel.apache.org/mail.html mentions MailProducer but I can't find an
example and the JavaDoc does not show it being used.
Can anyone provide an update to the documentation as I'm not aware of
whether we should be using it instead of an smtp: endpoint.
Thanks,
James
17 matches
Mail list logo
