Re: using camel as "generic relay"

Hi Claus, the answer from Willam is exactly what we expected. Best regards, Mario Claus Ibsen-2 wrote: > > Hi > > Did you get any help with this or did you find some answers yourself? > > I am not to familiar with CXF interceptors but the CXF team is of course. > And Willem Jiang as well a

Set charset to utf-8 for sending emails using smtp endpoint

I am trying to set the content type of the mail I send using the contentType header. That doesn't work, but it works if I put the contentType in the endpoint uri. i.e. - text/html Has no effect, while this works - smtp://roh...@xyzab.pramati

Re: Set charset to utf-8 for sending emails using smtp endpoint

Hi Looks like a bug/feature we should support. Could you create a ticket in JIRA? Link to JIRA from here: http://camel.apache.org/support.html On Mon, May 25, 2009 at 10:17 AM, rohitbrai wrote: > > I am trying to set the content type of the mail I send using the contentType > header. That does

Re: If condition is met then we can continue the process ?

Can I put a "content message router" between the split() and the end() ? e.g. *from("queue:in")* --> contain list of Order POJOs. Each list represents an unit (coming from a file) and must be processed as such ... *transacted()* --> order saving in the DB and list of POJOs to be put in the queues

Problems with error handling in transactional client

Hi everyone, my route receives messages from a durable activemq topic and writes these to a database. Now I tried to enhance the route with transactions, that worked so far, but I also want to configure the Transactional Error Handler to retry forever and not only six times. I configured tra

Re: Problems with error handling in transactional client

Hi Yeah TX and error handling is hard. For background on error handling in Camel start from here: http://camel.apache.org/error-handling-in-camel.html Basically you cannot use TX with DeadLetterChannel. All redelivery and whatnot is totally in the hands of the backing system. So you should d con

Re: If condition is met then we can continue the process ?

On Mon, May 25, 2009 at 1:34 PM, Charles Moulliard wrote: > Can I put a "content message router" between the split() and the end() ? Yeah you should be able to nest as your like. So give it a try. If it gets to complex in one route, you can split it into smaller sub routes and link using "direct"

JAXB Exception

I am getting a "Caused by: javax.xml.bind.JAXBException: "org.helios.routing.server.EndpointInformation" doesnt contain ObjectFactory.class or jaxb.index" exception when attempting to execute the following route: public void configure() throws Exception { from("direct:ping

Re: JAXB Exception

Is there an ObjectFactory or a jaxb.index file in the package of org.helios.routing.server.EndpointInformation ? Can you double check it ? If not , JAXB can't do the marshal and unmarshal work for you. Willem Frank C. wrote: > I am getting a "Caused by: javax.xml.bind.JAXBException: > "org.helio

Re: JAXB Exception

Hmm - I think you should be providing a path to the JAXB marshaller, not a class name. Try: jaxb.setContextPath("org.helios.routing.server"); Best, Ade Frank C. wrote: I am getting a "Caused by: javax.xml.bind.JAXBException: "org.helios.routing.server.EndpointInformation" doesnt contain O

Re: JAXB Exception

Willem and Ade: What worked is trimming the string to "org.helios.routing.server" as well as adding the jaxb.index to the org.helios.routing.server. While it works, I don't have the need to do so much work (the types are all @Xml annotated) when using JAXB directly. e.g:

Re: JAXB Exception

JAXB DataFormat supports to set the JaxbContext. Please try these code, JaxbDataFormat jaxb = new JaxbDataFormat(); jaxb.setContext(JAXBContext.newInstance(EndpointInformation.class)); Willem Frank C. wrote: > Willem and Ade: > > What worked is trimming the string to "org.helios.routing.server"

Re: JAXB Exception

Works like a baby!!! Thanks, Frank willem.jiang wrote: > > JAXB DataFormat supports to set the JaxbContext. > Please try these code, > JaxbDataFormat jaxb = new JaxbDataFormat(); > jaxb.setContext(JAXBContext.newInstance(EndpointInformation.class)); > > Willem > > Frank C. wrote: >> Willem

1.6.1 spring namespace confusion

Hi there, When using v.1.6.1 I find myself still having to use the old spring namespace i.e.: http://activemq.apache.org/camel/schema/spring ...which of course is contrary to the namespace recommended at: http://camel.apache.org/spring.html Does the wiki page need to be updated to reflect wha

Re: 1.6.1 spring namespace confusion

We don't change the camel-1.x schema's target namespace to maintain the back compatibility. Here is a FAQ entry[1] which may help to you. [1] http://cwiki.apache.org/CAMEL/how-to-validate-the-camel-1x-context-xml-from-apache-camel-web-site.html Willem huntc wrote: > Hi there, > > When using v.1.

Re: 1.6.1 spring namespace confusion

I shall update the wiki to reflect this situation unless there are objections. -- View this message in context: http://www.nabble.com/1.6.1-spring-namespace-confusion-tp23716403p23716923.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

throwFault deprecated - what is the equivalent for 1.x?

Hi there, Now that throwFault has been deprecated in 1.6.1, what should I be using to avoid strike throughs and warnings in my pretty code. :working: Christopher -- View this message in context: http://www.nabble.com/throwFault-deprecated---what-is-the-equivalent-for-1.x--tp23717019p23717019.h

Re: throwFault deprecated - what is the equivalent for 1.x?

Hi I believe there should be a setFault method. On Tue, May 26, 2009 at 7:32 AM, huntc wrote: > > Hi there, > > Now that throwFault has been deprecated in 1.6.1, what should I be using to > avoid strike throughs and warnings in my pretty code. :working: > > Christopher > -- > View this message i

Re: throwFault deprecated - what is the equivalent for 1.x?

Hi Claus, There is a setFaultBody and a setFaultHeader but I am not sure of how to use these in place of throwFault. Do you have an example? Here's what I presently do: ... .otherwise() .throwFault( "Unknown notification sent by fingerprint reader"); Thanks for your time. Kind regards,

Re: throwFault deprecated - what is the equivalent for 1.x?

On Tue, May 26, 2009 at 7:54 AM, huntc wrote: > > Hi Claus, > > There is a setFaultBody and a setFaultHeader but I am not sure of how to use > these in place of throwFault. Do you have an example? Here's what I > presently do: > > ... >  .otherwise() >  .throwFault( >    "Unknown notification sent

Re: throwFault deprecated - what is the equivalent for 1.x?

Thanks Claus. I presume you meant: .setFaultBody(constant("Unknown notification sent by fingerprint reader")) -- View this message in context: http://www.nabble.com/throwFault-deprecated---what-is-the-equivalent-for-1.x--tp23717019p23717251.html Sent from the Camel - Users (activemq) mailing l

Re: throwFault deprecated - what is the equivalent for 1.x?

On Tue, May 26, 2009 at 8:06 AM, huntc wrote: > > Thanks Claus. I presume you meant: > > .setFaultBody(constant("Unknown notification sent by fingerprint reader")) Yeah :) Looks like it accepts a Expression as parameter. Maybe we should add a String as well as its common to set a String body. But

Re: throwFault deprecated - what is the equivalent for 1.x?

I presume that setFaultBody has the same behaviour as throwFault right? My goal is to throw an exception and have the message got to the dead letter channel for retry processing. Thanks again. -- View this message in context: http://www.nabble.com/throwFault-deprecated---what-is-the-equivalent

Re: throwFault deprecated - what is the equivalent for 1.x?

On Tue, May 26, 2009 at 8:13 AM, huntc wrote: > > I presume that setFaultBody has the same behaviour as throwFault right? > > My goal is to throw an exception and have the message got to the dead letter > channel for retry processing. Yes it has the same behavior. throwFault did not really throw