- This topic has 2 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
hi everybody,
i was playing around with multipart messages, and i built an orchestration that succesfully created a mutipart message:
MyMultiPartMsg.Part1 = MessageBasedOnSchema1;
MyMultiPartMsg.Part2 = MessageBasedOnSchema2;
using the orchestration debugger, i can clrealy see that the "MyMultiPartMsg" is successfully built and it contains the two message parts.
now i tried to send message "MyMultiPartMsg" through a file send adapter, but i ended with a single file representing "MessageBasedOnSchema1" !!!
clearly there is something about sending multipart messages out through orchestrations, that i do not understand.
i would appreciate any explanation on the above and how to fix it.
reagrds,
-
The FILE adapter doesn't know how to deal with multi-part messages natively, since a single file would naturally only know how to deal with a single message part. The SMTP adapter, by contrast, knows how to do it since multi-part messages are very normal in email (think attachments).
That said, you can use the MIME/SMIME encoding component on a send pipeline with the FILE adapter and it will output a single file that contains all message parts encoded using MIME, I think.
-
You will only get a file with the part marked as ""body", as the previous post said, you will need a custom send pipeline with MIME, then if you use the file adapter with the mask set to the extension ".eml" you will be able to open it with you email client (outlook for example) and you’ll see the all the parts as email attachments (or the body part as email body and then all the other as attachments depending on how you configured the MIME component.
Enrique
http://www.BiztalkAnd.Net/blog
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.