onfiguration 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:claus.ib...@gmail.com]
gt; 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:claus.ib...@gmail.com]
> Sent: Wed
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:claus.ib...@gmail.com]
Sent: Wednesday, May 06, 2015 11:35 AM
To: users@camel.apache.org
Subject: Re: Camel Mail
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 wrote:
> I expect the
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.
Hi
What would you expect to happen? The option is a flag to turn lazy
mapping on or off.
On Wed, May 6, 2015 at 4:41 PM, wrusch wrote:
> I am testing with camel-mail 2.14.
>
> I am testing both pop3 and imap email consumers.
>
> When i toggle the mapMailMessage flag nothing changes at all with t
