Hi
Ad 1) If you are using the DeadLetterChannel in Camel to handle the retry then it populates the exchange with information about: - retry count - marked as redelivered - the caused exception A little info here: http://activemq.apache.org/camel/dead-letter-channel.html And there should be an exchange.getException() to get the caused exception. And there is also a exchange.isFailed() method to return if the exchange was OK or NOT. About HTTP, FTP and SFTP. If you are using them from Camel to communicate to an external system (use them as producers) then yes. If Camel can not for instance connect with the remote FTP server it will return the caused exception. Usually wrapped in a CamelRuntimeException with the original cause. BTW: You can configure the DeadLetterChannel in Camel to use all kind of waiting strategy between retries = RedeliveryPolicy. http://activemq.apache.org/camel/maven/camel-core/apidocs/org/apache/camel/processor/RedeliveryPolicy.html Ad 2) Could you write a small sample with the problem and create a ticket for it in JIRA, then it's not forgotten and we could take a look. Ad 3) You can use the property placeholder in some situations. We have a ticket to support it 100% in the future. See this FAQ entry: http://activemq.apache.org/camel/how-do-i-use-spring-property-placeholder-with-camel-xml.html Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: harinair [mailto:[EMAIL PROTECTED] Sent: 19. september 2008 03:30 To: [email protected] Subject: Some questions Hi All: I recently started working with Camel since our organization does a lot of message routing. We have a bunch of custom code written to do message routing and the plan is to replace this with Camel on the long run. And as a part of the effort we are planning to use Camel for a project that is coming up. However I have couple of doubts: 1. We are sending messages dynamically to different endpoints using recipientList. One message currently goes to one endpoint. However I would like to save the delivery status (whether failed or success) of each message in database. I currently put the messages on delivery-queue and then try to send out from there. On errors I move it to redelivery-queue using deadLetter processing. But I do some more retries there (reason for doing that is to have bigger retry interval and not to hold up messages coming through delivery queue) and if it fails again it goes to the dead-letter-queue. Now in database I have to set whether a particular message failed or is successful (even better if I can set the status as "retrying"). We also need the exception stack if possible. Can it be done? Can the HTTP, SFTP, FTP modules give back the Exception information? 2. I am also having difficulty using header names in xpath if the names have periods in them. How do we solve that? For example if a header name is "my.nice.header" then using it as $my.nice.header creates errors. Probably there is a way to escape periods? 3. I have seen documentation suggesting that the Spring PropertyPlaceHolderConfigurer is not supported within camel routes. Some other document suggested it will be supported in future. Does Apache Camel 1.4.0 support PropertyPlaceHolderConfigurer and if so any documentation? I will highly appreciate, if some Apache Camel Guru can answer these questions. Regards, Hari Gangadharan -- View this message in context: http://www.nabble.com/Some-questions-tp19564827s22882p19564827.html Sent from the Camel - Users mailing list archive at Nabble.com.
