[
https://issues.apache.org/jira/browse/CAMEL-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dr. Martin Menzel updated CAMEL-4093:
-------------------------------------
Attachment:
CAMEL-4093_with_adapted_unit_test_regarding_MailMessageClass.diff
When I understood Claus's comment right, the special MessageType can be used to
deliver the mailapi Message Object.
So to pipe this message over several steps we would have to write our own
processor to transform the Message Object to a serialized Type (like String)
before deliver this serialized Object to for example a file component.
In the attached modified unit test you find a example where the Message is
multicast to a mock and to a file component. Without an intermediate Processor
the proposed type converter mechanism leads to a null pointer exception.
Any comments to my thoughts are welcome.
> pop3 component parameter deliverRawMailMessage
> ----------------------------------------------
>
> Key: CAMEL-4093
> URL: https://issues.apache.org/jira/browse/CAMEL-4093
> Project: Camel
> Issue Type: New Feature
> Components: camel-mail
> Affects Versions: 2.7.2
> Environment: Solaris and Windows
> Reporter: Dr. Martin Menzel
> Assignee: Richard Kettelerij
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4093.diff,
> CAMEL-4093_with_adapted_unit_test_regarding_MailMessageClass.diff,
> CAMEL-4093_with_unit_test.diff
>
>
> Old Subject: s/Mime signed Mails lead to Exceptions in pop3 component
> If a s/mime signed Mail is received by the pop3 Mail component a expection is
> thrown during handling the body of the message. This happens because a
> different type of body object is delivered by javamail.
> I fixed this issue by introducing a new parameter which makes it possible to
> deliver the complete mail source in the Camel message body. In this way you
> are able to handle the content with processors in a very flexiable way.
> ------------ additional remark -------------
> During my preparation of testcases I reduced the complexity of my former
> project, removed classpath jars just to the basics jars needed to run pop3
> retieval. In this situation I don't get the error anymore (for Java DSL and
> Spring configuration).
> => The included patch is therefore just a new feature which is helpfull if a
> processor/consumer would like to get the complete mail source instead of just
> the payload. This can be controlled by a new pop3 component uri parameter
> deliverRawMailMessage
> example spring URL:
> pop3s://[email protected]?password=pazzword&debugMode=true&deliverRawMailMessage=true
> I will deliver a unit test which tests the different behavior without
> disturbing the normal way of delivering mail content.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
