Hi I found a spot for improving https://issues.apache.org/jira/browse/CAMEL-8779
Thanks for spotting this. On Sun, May 17, 2015 at 8:37 AM, Claus Ibsen <[email protected]> wrote: > Hi > > Yeah the uow copy would cause the message to be initialized. You can > however turn off allowUseOriginalMessage which is what Camel also > recommends if you dont need that functionality, and the copy is not > needed. > > On Wed, May 6, 2015 at 6:36 PM, <[email protected]> wrote: >> Can you tell me what I would look for in the exchange to tell the difference. >> >> At the very first line of the very first processor coming directly off of >> the imap endpoint, I put a debug break point. >> >> This is absolutely the first place in the code where I as a camel user can >> do anything with the exchange. >> >> With mapMailMessage set to false, I inspect the message and every single >> mail message header is already mapped to the MailMessage headers map. >> >> When I look further up the code stream I see that the mapping is happening >> always during the construction of DefaultUnitOfWork while doing internal >> standard advice as part of the CamelInternalProcessor. At which point it is >> doing an message copy. >> >> There is no way to avoid this (at least that I know of) and there is >> obviously nothing mail client specific code at that point of the exchange. >> >> Since the configuration point changes nothing in how the exchange is >> processed I will assume this is bug resulting in a completely dead and >> useless configuration point. >> >> >> >> -----Original Message----- >> From: Claus Ibsen [mailto:[email protected]] >> Sent: Wednesday, May 06, 2015 11:35 AM >> To: [email protected] >> Subject: Re: Camel Mail mapMailMessage flag ignored >> >> Hi >> >> Read the description. Its about whether mail message headers and body is >> mapped to Camel Message Body / Headers automatic or lazy-on-demand. >> >> From outside you cant tell the difference unless you work with the low level >> message api. >> >> On Wed, May 6, 2015 at 5:32 PM, wrusch <[email protected]> wrote: >>> I expect the flag to do something? >>> >>> I really don't understand your reply. >>> >>> No matter what value I set, nothing changes. >>> >>> For pop3 the mapping happens 'never' >>> For imap the mapping happens 'always' >>> >>> In either case the flag does nothing at all. >>> >>> >>> >>> -- >>> View this message in context: >>> http://camel.465427.n5.nabble.com/Camel-Mail-mapMailMessage-flag-ignor >>> ed-tp5766767p5766771.html Sent from the Camel - Users mailing list >>> archive at Nabble.com. >> >> >> >> -- >> Claus Ibsen >> ----------------- >> Red Hat, Inc. >> Email: [email protected] >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen >> hawtio: http://hawt.io/ >> fabric8: http://fabric8.io/ >> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: [email protected] > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
