Does Camel-Mina work with version 2 of Apache Mina

Use of the camel-mina v 2.6.0 dependency in a Maven pom downloads mina-core.1.1.7. Does this mean I can use camel-mina with v 2 of Apache Mina. Is there a new version of camel-mina that depends on Mina 2? -- View this message in context: http://camel.465427.n5.nabble.com/Does-Camel-Mina-work-wi

Posting to Camel Servlet endpoint brings up file download dialog

I need help configuring Camel Servlet route so that when I post a form to the endpoint, , I don't get the file download dialog Firefox. I've tried everything I can think of to elminate the dialog but to no avail. I just use a simple route (from the tomcat servlet example on the Camel Servlet web

Re: Posting to Camel Servlet endpoint brings up file download dialog

Thanks for the tip. So...how else does one submit? -- View this message in context: http://camel.465427.n5.nabble.com/Posting-to-Camel-Servlet-endpoint-brings-up-file-download-dialog-tp3424535p3425276.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: publishedEndpointUrl for cxf:cxfEndpoint

I don't believe this is correct, simply to change the address in the cxfEndpoint. I have a similar firewall problem and need to expose a camel-cxf endpoint running behind a firewall. My endpoint is defined as follows: But a client needs to access this from the outside, as https://someURL:4443/Pr

Splitter StopOnException doesn't forward the exception on the Exchange

I have the following route which uses stopOnException to catch exceptions: The processSegment bean in the above route can throw the following exception: throw new Exception("Product, " + vendorndc + ", is not in formulary"

Re: Splitter StopOnException doesn't forward the exception on the Exchange

Yes. I'm using camel v2.71. Here is my error handler: and the deadletter route is: The queryFormularyErrorHandler refers to the QueryFormularyErrorHandler processor described earlier, and the createReturnMsg bean just translates the exception message into a

Re: Splitter StopOnException doesn't forward the exception on the Exchange

So, if I understand you correctly, I shouldn't use the DeadLetterChannel type in the error handler. What types are available and how would I then configure the error handler? -- View this message in context: http://camel.465427.n5.nabble.com/Splitter-StopOnException-doesn-t-forward-the-exception-

Re: Splitter StopOnException doesn't forward the exception on the Exchange

I don't believe the AggregatorStrategy is the problem, but here is mine: public class DispensingAggregationStrategy implements AggregationStrategy{ public Exchange aggregate(Exchange oldExchange, Exchange newExchange) { if (oldExchange == null)

camel-cxf service publish address problem

I have a camel-cxf application running in Tomcat behind a proxy with the following camel-cxf.xml: I would like to change "myservername:8890" in the endpoint address attribute to "localhost:8890", but it doesn't work, i.e, I can't get to the wsdl at the published endpoint URL (with"?wsdl" appende

What's best practice for running Camel 2.9.0 in JBOSS 5.X

I want to run a camel route in a JBOSS 5.X instance in order to send messages via a Camel proxy to a remote service which is running an activemq broker. Should I put the route and accompanying proxy interface in a jar file and launch it in the JBoss instance lib directory, or package it as a war

Error: cannot run camel-servlet version 2.9.1 in Tomcat

I changed the camel version in the camel-example-servlet-tomcat pom.xml from the apache-camel-2.8.1 package, and got the following error trying to run *mvn package tomcat:run*; java.lang.ClassCastException: org.apache.camel.component.servlet.CamelHttpTransportServlet cannot be cast to javax.servl

Re: Error: cannot run camel-servlet version 2.9.1 in Tomcat

I'm using jdk1.6.0_26 and Tomcat 6.0.33. But that seems hardly relevant. Just change the camel version in the pom back to the original - 2.8.1, and the darn thing runs. Did you run the example?Something's broken in camel v 2.9.x. And, no, servlet.jar is not in WEB-INF/lib. -- View this message in

Re: Error: cannot run camel-servlet version 2.9.1 in Tomcat

Ah. I stand corrected, somewhat. Camel servlet 2.9.1 inserts geronimo-servlet_2.4_spec-1.1.1.jar in the war file, whereas v 2.8.1 does not. It seems, therefore, that the newer camel is not web application server friendly. out of the box. -- View this message in context: http://camel.465427.n5.nab

How can I send a file to a remote ftp server using the ftp2 component

All of the examples I have seen show how to retrieve files from a remote ftp server using the ftp component, but I need to send files. In my processor, I create a ProducerTemplate and try to send the file like so: ProducerTemplate template = exchange.getContext().createProducerTemplate(); String

Re: Error: cannot run camel-servlet version 2.9.1 in Tomcat

Here is the maven dependency tree. As you can see, the camel-servlet verson 2.9.1 has a transitive dependency on javax.servlet, from the http component. Obviously, while the 2.8.1 version scopes this as "provided", apparently that is not the case with version 2.9.1. Building Camel :: Example ::

Re: Error: cannot run camel-servlet version 2.9.1 in Tomcat

I see where the errant jar was introduced. It was in the v 2.8.1 parent pom versioning. Simply changing the version of some of the camel components in the project's pom was not sufficient due to maven's transitivity. -- View this message in context: http://camel.465427.n5.nabble.com/Error-cannot