Claus, I'm not a contributor on the Camel project, but here's what I would
advocate trying in MailBinding.java, expanding the meaning of
"ignoreUnsupportedCharset" a bit:
public Object extractBodyFromMail(Exchange exchange, Message message) {
return extractBodyFromMail(exchange, messa
thanks guys. I added some parameters to the queue to make the route
"transactional"...
from("activemq:inboundMessages?maxConcurrentConsumers=50&lazyCreateTransactionManager=true&transacted=true")
.process(new Processor1())
.process(new Processor2())
.to("activemq:finishedQueue");
Now I'm getti
Thanks for the reply - I was only able to get my route working by using a
Spring Transaction Manager to open a new transaction (using
PROPOGATION_NOT_SUPPORTED) to do the actual publish request/reply part of
the route (just wrapped the producer template publish in this transaction).
That worked.
On Wed, Nov 4, 2009 at 9:27 PM, ronP12 wrote:
>
> Hello,
> I am using the SFTP component and I want to change the file name when it is
> placed on the remote server. Basically I would like it to behave like:
>
> from(file:/tmp/input.txt).
> to("sftp:/./directory/output.txt)
>
> I trie
Yeah as Christian says you need to use transactions for that.
On Wed, Nov 4, 2009 at 8:23 PM, Christian Schneider
wrote:
> As far as I know the transactional client aproach is the only good way to
> guarantee that no message is lost.
> You can take a look at these pages:
> http://camel.apache.or
On Wed, Nov 4, 2009 at 7:24 PM, dcheckoway wrote:
>
> Is there any way to "intercept" the raw mail message content before it gets
> passed to the java mail API? I would be happy to manually munge the
> Content-Type header if I detect one of the known-to-be-funky charsets in
> there.
>
You can us
Hello,
I am using the SFTP component and I want to change the file name when it is
placed on the remote server. Basically I would like it to behave like:
from(file:/tmp/input.txt).
to("sftp:/./directory/output.txt)
I tried to manipulate the header using.
setHeader("ou
As far as I know the transactional client aproach is the only good way
to guarantee that no message is lost.
You can take a look at these pages:
http://camel.apache.org/jms.html section: Enabling Transacted Consumption
http://camel.apache.org/transactional-client.html section: Camel 2.0 -
JMS
I'm using Camel2 in SMX 3.3.1. I have a simple Camel route as follows...
from("activemq:inboundMessages?maxConcurrentConsumers=50")
.process(new Processor1())
.process(new Processor2())
.to("activemq:finishedQueue");
How do I guarentee that a message will not be removed from the
"inboundMessage
Is there any way to "intercept" the raw mail message content before it gets
passed to the java mail API? I would be happy to manually munge the
Content-Type header if I detect one of the known-to-be-funky charsets in
there.
Claus Ibsen-2 wrote:
>
> On Wed, Nov 4, 2009 at 4:57 PM, dcheckoway
> You can just use Apache Karaf which is a very lightweight OSGi kernel.
+1 that's the one to use if you are short on space.
--oh
Even by removing the exchange.setOut I am not seeing the header I've added
when checking the exchange In message on the exception processor.
this is my current process for interceptSendToEndpoint:
public void process(Exchange exchange) throws Exception {
String deliveryEndPoint =
On Wed, Nov 4, 2009 at 4:57 PM, dcheckoway wrote:
>
> I'll definitely try 2.1-SNAPSHOT. And in the meantime, how would I go about
> "catching" that exception so that my app can at least be aware of this error
> condition?
>
> As of right now, it literally clogs the whole process, since Camel can'
On Wed, Nov 4, 2009 at 5:12 PM, mcrive wrote:
>
> I've configured following route:
>
> interceptSendToEndpoint("*").process(new SendToEndPointHandler());
>
> onException(GenericFileOperationFailedException.class)
> .process(new DeliveryFailureHandler());
>
> from("test-jms:queue:notificatio
I've configured following route:
interceptSendToEndpoint("*").process(new SendToEndPointHandler());
onException(GenericFileOperationFailedException.class)
.process(new DeliveryFailureHandler());
I'll definitely try 2.1-SNAPSHOT. And in the meantime, how would I go about
"catching" that exception so that my app can at least be aware of this error
condition?
As of right now, it literally clogs the whole process, since Camel can't get
past that offending message and process anything else i
On Wed, Nov 4, 2009 at 4:28 PM, Schneider Christian
wrote:
> Hi Claus,
>
> of course brokers like ActiveMQ have a great dead letter facility.
> Unfortunately we are stuck with Tibco EMS here.
> As it seems EMS by default will discard messages after the maximum number of
> redeliveries.
> You can s
Hi Johnathan,
To elaborate on Claus's reply. In general, you cannot really process InOut
exchanges inside a transaction (yes, there is a 'transactedInOut' option,
but it only applies to a very special use case and is not relevant to your
example).
The best approach, as Claus suggested, is to spl
Hi Claus,
of course brokers like ActiveMQ have a great dead letter facility.
Unfortunately we are stuck with Tibco EMS here.
As it seems EMS by default will discard messages after the maximum number of
redeliveries.
You can set a property JMS_TIBCO_PRESERVE_UNDELIVERED=true to make Tibco
deliver
On Wed, Nov 4, 2009 at 2:48 PM, mcrive wrote:
>
> 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?
>
You can use interceptSendToEndpoint
http://davsclaus.blogspot.com/2009/05/on-road-to-camel-20-interceptors-round.h
On Wed, Nov 4, 2009 at 2:56 PM, Schneider Christian
wrote:
> Hi Willem,
>
> that is fine with me. I have closed the ticket.
>
> I have another exception problem though. I want to define a rule for the
> other exceptions that should not return a fault. I want these exceptions to
> be forwarded into
Hi Willem,
that is fine with me. I have closed the ticket.
I have another exception problem though. I want to define a rule for the
other exceptions that should not return a fault. I want these exceptions to
be forwarded into something like a dead letter queue after some retries.
I see two diff
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(GenericFileOperationFailedException.class)
>>
On Wed, Nov 4, 2009 at 2:40 PM, mcrive wrote:
>
> I ha following route
>
>
> onException(GenericFileOperationFailedException.class)
> .process(new DeliveryFailureHandler()).stop();
>
>
> from("test-jms:queue:feed.notificationtest.queue")
> .process(processor)
> .recipientList(
I ha following route
onException(GenericFileOperationFailedException.class)
.process(new DeliveryFailureHandler()).stop();
from("test-jms:queue:feed.notificationtest.queue")
.process(processor)
On Wed, Nov 4, 2009 at 10:53 AM, DRy wrote:
>
> Hi,
>
>
> Claus Ibsen-2 wrote:
>>
>> I guess JPA has instrumented and all sorts to those objects so you
>> cant serialize them and send them over the remote network.
>> Maybe there is something in the JPA API to detach or what it may be
>> called fro
Hi,
Claus Ibsen-2 wrote:
>
> I guess JPA has instrumented and all sorts to those objects so you
> cant serialize them and send them over the remote network.
> Maybe there is something in the JPA API to detach or what it may be
> called from the JPA EntityFactory so you can send it over network.
27 matches
Mail list logo
