Why not just letting the deadLetterChannelhandler send the exchange into
a mail endpoint like this ?
errorHandler(deadLetterChannel(smtp://[usern...@]host[:port][?options])
.useOriginalMessage().mamimumRedeliveries(5).redeliverDelay(5000);
On 10/19/10 9:01 PM, Andreas A. wrote:
Hi
I'm
Hi,
You can take a look at this doc[1], and put the class into the class
path to let camel context load it.
[1]http://camel.apache.org/class.html
On 10/19/10 11:29 PM, Remi Malessa wrote:
Hi , I'm new to Camel.
I'm familiar with ActiveMQ and I would like to move my JMS Client
entirely to a
That could be an option, but I also have parts of the application that are
not in Camel-routes that I would like to get e-mailed about. Thought it
would be easier/cleaner to just have it configured in the logging.
--
View this message in context:
That looks good.
And I think activemq's lib directory is the right place for my classes ,
uploaded as a jar?
Will give it try.
Thanks!
Remi
On 10/20/2010 08:53 AM, Willem Jiang wrote:
Hi,
You can take a look at this doc[1], and put the class into the class
path to let camel context load
Do you need exclusive read lock on those files?
When the files is being dropped into that FTP folder are they already done?
For example write to a temp folder and then move the file (atomic OS
operation)
If so you can use readLock=none.
Its generally best to have a strategy where the producer
Just a quick reminder of our survey. It runs till the end of the month.
With Apache Camel moving fast towards its 3.0 version we need to
understand the areas where we need to focus our attention and efforts.
We want to know you, our users, better and learn from your experiences
and struggles
A few weeks ago, I started a thread on the Camel dev channel [1] about
loosing messages if I use non persistent messaging with ActiveMQ. The broker
shoot down, if the single, non persitent connection was closed and start the
broker again, if I open a new connection to it (I have to configure the
See this link about posting form nabble
http://camel.apache.org/discussion-forums.html
The preMove is done after a lock has been acquired. Camel will only start
working on the file if the lock has been acquired.
--
View this message in context:
The JMS consumer is broker specific and in your case I assume its WebLogic.
So go ask BEA/Oracle about how their JMS consumer (client) can load balance
with multiple JMS servers.
--
View this message in context:
Hallo
The intention of our developing issue was to call, a soap webservice from
camel via the producertemplate.
As base of our researching we used this site.
http://camel.apache.org/soap.html http://camel.apache.org/soap.html
Proxy code generation with wsdl to code generators, should not be
Hi Fitzgerald,
the Soap Dataformat only works if you generate code for the wsdl. Internally
the dataformat analyzes the generated classes and does the mapping to soap
using these.
Honestly I don´t understand how this should work without the generated classes.
Do you still want to call the
Yeah, the SoapDataFormat is based on the JAXB which is need to use the
generated classes to do marshal and unmarshal work.
If you already has the generate soap message you can consider to use
camel-http component to do the proxy job.
On 10/20/10 9:16 PM, fitzgerald wrote:
Hallo
The
Hallo Christian
Thanks for your answer.
During some days of debugging through camel, I got the same opinion like you
descibed in your answer.
I wanted to be sure, not to have overseen something.
Thanks
Fitzgerald
--
View this message in context:
Hallo Willem
I also had that possibility in mind, but for me it only makes sense when
there are only a small number of such webservices, and the passed data won't
be changed so excessive.
The most pragmatic and error preventing way is, to use the client classes
und Clienthelper classes itself.
Is there any reason why you wanted to get rid of the code generation?
Thanks
Christian
Christian Schneider
Informationsverarbeitung
Business Solutions
Handel und Dispatching
Tel : +49-(0)721-63-15482
EnBW Systeme Infrastruktur Support GmbH
Sitz der Gesellschaft: Karlsruhe
Handelsregister:
So I guess it worked for jms and file because the data is serialized using java
serialization. Is that true?
Theoretically you could manually annotate the classes to be serialized with
jaxb annotations. In this case you would not need code generation. Currently
the soap data format does not
You can build your own camel component which supports SFTP in Camel 1.x.
At Apache we are not going to backport the code for you. Camel 1.x is being
EOL at the end of the year
http://camel.apache.org/2010/09/28/camel-riders-to-discontinue-support-for-1x-branch.html
--
View this message in
How do I configure (total) timeouts for exchanges?
I have different components in the routes, and I do not want to configure
component timeouts. What I need is, to configure a total timeout so that any
exchange would stop/exit the route if it times out.
Thanks.
-
- Karthz
--
View this
Hi Hossein,
Before Camel 2.3.0, we don't support the selector in CamelConsumerTemplate.
Anyway the selector option is an SQL92 predicate. Some character such as
= should be encoded as %30 to be interpreted by Camel.
Regards
JB
On 10/20/2010 10:19 PM, Hossein wrote:
Hello,
Using camel
Based on your suggestion I've wrote this
from(FTPS_ENDPOINT
+?password=gustavomove=processed?localWorkDirectory=+ localWorkFolder)
.beanRef(parser, convert)
.to(FTPS_ENDPOINT
+/out?password=gustavofileName=${file:onlyname})
;
but for some reason the
I would suggest you assign a timestamp and an expiration time to
properties on the exchange at the beginning of the route, then use
intercepts to check the exchange as it gets processed.
http://camel.apache.org/intercept.html
Don
On Wed, Oct 20, 2010 at 1:32 PM, Karthz skart...@gmail.com wrote:
Hi Christian,
Thanks for sharing this with the camel community.
It just rang the bell to remind me there is an explanation[1] for your
issue :)
BTW, for most camel jms test, we don't depends on the activemq-camel
component, I will give the CachingConnectionFactory a try.
Hi there,
you need to pass the = as %3D as stated in the component docs.
See:
http://camel.apache.org/jms.html
So it would be:
from(activemq:queue:somequeue?selector=clientid %3D
'someid').to(someOtherQueue)
Bye,
Norman
Am 20.10.2010 22:19, schrieb Hossein:
Hello,
Using camel 2.2, I'm
This should have been fixed in Camel 2.5
You can use a fixed reply to queue to work around this issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Routes-throws-TimeOutException-after-ESB-restart-tp3229609p3229883.html
Sent from the Camel - Users mailing list
24 matches
Mail list logo
