[
https://issues.apache.org/jira/browse/AXIS2-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651460#action_12651460
]
Thilina Gunarathne commented on AXIS2-4153:
-------------------------------------------
http://svn.apache.org/viewvc?rev=721338&view=rev
> Creation of a MessageBuilder that can handle any email message
> --------------------------------------------------------------
>
> Key: AXIS2-4153
> URL: https://issues.apache.org/jira/browse/AXIS2-4153
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Asankha C. Perera
> Assignee: Thilina Gunarathne
>
> Require a message Builder implementation, that can parse *any* valid Email
> message
> If the message contains any attachments, they need to be available as
> attachments in the Axis2 MessageContext as usual. The builder should be able
> to digest *any* type of attachment, irrespective of its content type (e.g.
> zip, jpg, csv, raw binary, junk etc) All thats expected is the ability to
> "get to these" attachment data from the higher level application code.
> If the message contains typical message body, that needs to be mapped to the
> SOAP envelope body. Thus, we should give preference to SOAP 1.2/1.1, POX,
> text/plain and text/html in that order (in my personal pov which should be
> validated) to construct the main envelope body, if/when multiple parts are
> available. If a decision cannot be made to pick one, I think we could leave
> all as attachments. For alternative parts, I think its typically text vs
> html, and we should pick text (or make that configurable)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
