Camel meven goal configuration problem
Hi all, I am trying to run camel maven goal (camel:dot). I stated that if in resource project folder, it does not exist META-INF/spring:*.xml structure, but something like resource/ com/ myprganisation/ routes/ camel-context.xml (camel routes are in this file) Folder1/ SpringFile1.xml (beans used by camel routes) The command mvn camel:dot generate an index.html file with message No EIP diagrams available even if in my pom.xml, i configure applicationContextUri property of camel-maven-plugin. Is someone can explain me what is wrong in my use of camel maven goal ?:confused: Thanks in advance, Best regards. Mta38 -- View this message in context: http://www.nabble.com/Camel-meven-goal-configuration-problem-tp22369252p22369252.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: Camel meven goal configuration problem
Hi Could you show us you maven pom configuration for this plugin? On Fri, Mar 6, 2009 at 11:18 AM, mta38 mtaraud@orange-ftgroup.com wrote: Hi all, I am trying to run camel maven goal (camel:dot). I stated that if in resource project folder, it does not exist META-INF/spring:*.xml structure, but something like resource/ com/ myprganisation/ routes/ camel-context.xml (camel routes are in this file) Folder1/ SpringFile1.xml (beans used by camel routes) The command mvn camel:dot generate an index.html file with message No EIP diagrams available even if in my pom.xml, i configure applicationContextUri property of camel-maven-plugin. Is someone can explain me what is wrong in my use of camel maven goal ?:confused: Thanks in advance, Best regards. Mta38 -- View this message in context: http://www.nabble.com/Camel-meven-goal-configuration-problem-tp22369252p22369252.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
Starting, stopping and removing routes at runtime
There are some older post on this topic in the forum, but I could not figure out if the answers are still up to date. So is it possible to remove routes from the CamelContext to add updated ones at runtime? And what happens with messages on a route that are not delivered when the route stops or is removed? I'm currently evaluating Camel 1.6 and the 2.0 Snapshot to figure out if it works in my application, so any information about this would be very helpful for me. M.S. -- View this message in context: http://www.nabble.com/Starting%2C-stopping-and-removing-routes-at-runtime-tp22370230p22370230.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: Starting, stopping and removing routes at runtime
2009/3/6 m.s. da_...@arcor.de: There are some older post on this topic in the forum, but I could not figure out if the answers are still up to date. So is it possible to remove routes from the CamelContext to add updated ones at runtime? And what happens with messages on a route that are not delivered when the route stops or is removed? I'm currently evaluating Camel 1.6 and the 2.0 Snapshot to figure out if it works in my application, so any information about this would be very helpful for me. You can now stop and start routes in 2.0 SNAPSHOT - details in this thread and JIRA... http://www.nabble.com/starting%2C-stopping%2C-creating---editing-routes-at-runtime-now-worksCAMEL-1004-td22208810s22882.html#a22218251 -- James --- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
Wrong destruction order when using spring dsl
Hi all, we are using camel spring-dsl and we are routing from and to activemq. We are using camel:bean and camel:process I have the impression that in both cases the 'ref' property is not a real Spring reference (not wired by Spring) but is stored as a String and resolved later. Because of that, Spring is not aware of the dependency and might destroy the references before destroying the camel context. Additionally, there is no spring depency to the activemq component (it's just part of the uri), so it happens that the activemq connection pools get closed before the camel context. Can anybody confirm my impression? If so, is there a way to solve this problem? Thanks Thomas
Jetty-splitter-aggregator - reply
-- View this message in context: http://www.nabble.com/Jetty-splitter-aggregator---reply-tp22374389p22374389.html Sent from the Camel - Users mailing list archive at Nabble.com.
routing like jetty-splitter-aggregator-reply request/response problem
Hi, I'm building a routing like this : from jetty to splitter to aggegator to responseProcessor to mockend each endpoint is set to InOut and direct. Basically I want that request from jetty (that's like a batch to process) being splitted, processed (when all work), aggegated and have a response back. Instead what happen's that after splitted the last message is back as a response ... then the next endpoint will work fine but the (wrong) response is already back to jetty ... How can I tell to wait for a response by my responseProcessor ? Thanks to all try give me a suggest -- View this message in context: http://www.nabble.com/routing-like-%22jetty-splitter-aggregator-reply%22-request-response-problem-tp22374696p22374696.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Catch and handle errors when using the TransactionErrorHandler
On Fri, Mar 6, 2009 at 1:51 PM, Henric Hedin hhe...@gmail.com wrote: Hi, Is it possible to in some way to use the TransactionErrorHandler and at the same time catch and handle exceptions? I have read the documentation under http://camel.apache.org/error-handling-in-camel.html that for transactional exchanges the Error Handler does not kick, so the following code in my Route configure will not work: errorHandler(bean(TransactionErrorHandlerBuilder.class, transactionErrorHandler)); onException(SAXParseException.class). handled(true). policy(notsupported). maximumRedeliveries(1). transform().constant(Sorry, parse exception...). to(jms:queue:validationFailed.SAXParseException); from(jms:queue:input-queue?transacted=true). unmarshal(jaxbDataFormat). to(jms:queue:output-queue). What I'm trying to accomplish is if a parsing exception occurs, I would like my incoming message to be rolled back and put on the jms deadletter queue (configured for the queue on the JMS provider, when the JMSXDeliveryCount has reached it's threshold). But I would also be able to send an information jms-message to the same jms-provider with information about why the message has been backed out (of course outside the incoming transaction). Maybe a strange solution, but is it possible to handle in Camel? :) /Henric No the DeadLetterChannel is disabled for transacted exchanges. There is a trick though, if you dont add the Spring Policy then it will default to REQUIRED and still use DLC. We are considering how we can provide options for end users in the future so you can use DLC for somerthing combined with transacted exchanges. The problem with transacted exchanges is that they are redelivered in a totally new thread so Camel has no wait of correlating a previous attempt, we can only rely on the few JMS options you get such as the JMSX counter. But we dont know when we have reached exhausted, to send the extra JMS message But any feedback and ideas is welcome what we can do in the future to bring more value to error handling with TX -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
