Re: process() not called when mime type in Base64

Correction, the process() component is called! The Base64 convertor being selected does not popluate Exchange.getIn.getAttachments. Is this correct? -- View this message in context: http://www.nabble.com/process%28%29-not-called-when-mime-type-in-Base64-tp22539655p22540805.html Sent from the Ca

process() not called when mime type in Base64

Why is process() component in pipeline not called for route B? public class myApp extends SpringRouteBuilder { public static void main(String[] args) { new Main().run(args); } public void configure() { from("imap:mailhostA").process(new AttachmentProcessor("A")).to("be

Re: How do I filter out unwanted header properties propergated in route

That make sense, thanks Claus Claus Ibsen-2 wrote: > > On Fri, Mar 13, 2009 at 1:08 PM, AHardy wrote: >> >> Apache Camel has been a revelation in componentising flow based >> applications. >> Although getting started has been a hair pulling exercise at times..

How do I filter out unwanted header properties propergated in route

Apache Camel has been a revelation in componentising flow based applications. Although getting started has been a hair pulling exercise at times..but definitely rewarding. I have the following route defined from("imap:mailhost").process(new AttachmentProcessor).to("bean:translate").to("jms:queue: