Re: RMI Component in camel
Hi You can check out the unit test source code http://svn.apache.org/viewvc/camel/trunk/components/camel-rmi/ I guess the rmi wiki page could use an update. http://camel.apache.org/rmi.html If you get it working and feel like it, we would love feedback/countributions on this RMI component http://camel.apache.org/contributing.html Post back the working solution/feedback and I can help update the wiki page. On Tue, Feb 17, 2009 at 11:33 AM, Nivetha Shri nivis...@gmail.com wrote: Hi All Can someone tell me how to use RMI component in Camel? It is given tat we can hit the rmi service as follows.. from(inputEndPoint).to(rmi://localhost:1099/foo) I have bound the service as follows MyImpl obj = new MyImpl (); Naming.rebind(//localhost:1099/foo, obj); Usually, in a normal client we will invoke the rmi service as follows Hello obj = (Hello)Naming.lookup(//localhost:1099/foo); message = obj.myMethod(); i.e., we would get the object from the bindings and then invoke the methods that we do need. How can we achieve the same from camel? Any pointers to articles on this? Any help would be of great use. Thanks and Regards Nivi -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
Interceptor / stop / xml configuration file
Hi all, I want to use interceptor in my route. But I think I may do something wrong Here is my code route from uri=direct:a / intercept interceptor id=intercept1 ref=validateInterceptor/ to uri=mock:test/ stop/ /intercept to uri=direct:b/ /route … other routes … bean id=validateInterceptor class=com.example.interceptors.CheckMessageValidation/ My class CheckMessageValidation extends DelegateProcessor. The process method only adds a trace in a log file. When I test this route, I state that I have the expected trace in my log file, but all other routes are executed. The System does not stop after sending exchange to Mock endpoint. Can anybody can explain me what is wrong in my route. Best regards, Mta38 -- View this message in context: http://www.nabble.com/Interceptor---stop---xml-configuration-file-tp22054882s22882p22054882.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Interceptor / stop / xml configuration file
Hi You should only use the intercept tag, and then route to whatever you want to do route from uri=direct:a / intercept processRef ref=validateInterceptor/ to uri=mock:test/ stop/ /intercept to uri=direct:b/ /route But you can also route to a POJO and do what you like so you dont have to implement any Camel interfaces. intercept beanRef ref=someSpringBean/ to uri=mock:test/ stop/ /intercept On Tue, Feb 17, 2009 at 11:59 AM, mta38 mtaraud@orange-ftgroup.com wrote: Hi all, I want to use interceptor in my route. But I think I may do something wrong Here is my code route from uri=direct:a / intercept interceptor id=intercept1 ref=validateInterceptor/ to uri=mock:test/ stop/ /intercept to uri=direct:b/ /route … other routes … bean id=validateInterceptor class=com.example.interceptors.CheckMessageValidation/ My class CheckMessageValidation extends DelegateProcessor. The process method only adds a trace in a log file. When I test this route, I state that I have the expected trace in my log file, but all other routes are executed. The System does not stop after sending exchange to Mock endpoint. Can anybody can explain me what is wrong in my route. Best regards, Mta38 -- View this message in context: http://www.nabble.com/Interceptor---stop---xml-configuration-file-tp22054882s22882p22054882.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
Camel event handling code
I have written some code to add event handling to camel. From what I've read on the forums and a number of the JIRA tickets there seems to be a need for some type of event handling built into camel. If someone who is familiar with camel internals would take this code for a spin and see if the idea will work with the rest of camel architecture, maybe they can more properly implement some of the functionality I've added in my code. I'm not familiar enough with the entire camel system to know if this will work. Basically this code enables camel components and processors to send and receive events through the camel container. I've also attempted to add the function of starting and stopping routes with events, but it doesn't quite work right, and I'm not sure why. I can start routes with events, but stopping a route doesn't prevent processing which then causes camel to throw exceptions and stop working. There's a more descriptive explanation in the readme included in the zip. Hope this is useful. If not, feel free to toss it out. If there is a better way to do this type of thing than the with events then please let me know. I'm trying to figure out a way to conditionally start and stop routes. Thanks. The code in the zip file has the ASF license attached. http://www.nabble.com/file/p22058818/CamelEventCode.zip CamelEventCode.zip -- View this message in context: http://www.nabble.com/Camel-event-handling-code-tp22058818s22882p22058818.html Sent from the Camel - Users mailing list archive at Nabble.com.
Redeliver to end of Endpoint/Queue?
Is it possible to have an exchange/message that threw an exception during processing be redelivered to the end of the queue instead of staying at the front of the queue and holding up all messages that are behind it? Some sort of interceptor or callback or customization to DeadLetterChannel? I'm sure there are ways to do this, but what might be considered best practice? Thanks. Eric -- View this message in context: http://www.nabble.com/Redeliver-to-end-of-Endpoint-Queue--tp22060777s22882p22060777.html Sent from the Camel - Users mailing list archive at Nabble.com.
[ANN] Apache Camel 1.6.0 Release
The Camel team is pleased to announce the release of Apache Camel [1], version 1.6.0. This version features 169 issues fixed including: - two new components (freemarker and restlet) - numerous fixes in camel components (http, jetty, mina, ftp, etc) - DLC additions and improvements - improved testing - ... and much more Please see the Release Notes [2] for more details: [1] http://camel.apache.org/ [2] http://cwiki.apache.org/confluence/display/CAMEL/Camel+1.6.0+Release Enjoy, The Camel riders
Re: Redeliver to end of Endpoint/Queue?
After thinking about this some more, what I'd really like is to be able to consume a message at some time in the future. If an exception occurs during processing, instead of the processing thread sleeping for the delay period, the message should be re-delivered with something like a consume_time header. Then the message consumer will change its selector every time it polls, something like consume_time System.currentTimeInMillis() Thoughts anyone? -- View this message in context: http://www.nabble.com/Redeliver-to-end-of-Endpoint-Queue--tp22060777s22882p22071417.html Sent from the Camel - Users mailing list archive at Nabble.com.
