Other primitive Types would be serialized similarly. While correct, this is not what we expect. Nevertheless, creating string output from an Orchestration is relatively easy. This article describes two already well knows ways to create plain text string content in an Orchestration. Note: I am aware of the ability to create a custom Formatter and the sample that changes the serialization behavior of the Orchestration String Type.
Most of us have been producing string content from our BizTalk apps since the very beginning in the form of Flat Files. In fact, when this situation does come up, my recommendation is to simply treat the string as a Flat File message. The Sample application uses a Flat File Schema to produce string output. For simple string content, a Flat File is the best choice in the vast majority of cases, but if you string is a bit more than just a string, such as HTML, or is composed of many incoming elements, then producing the string from XSLT is the next option.
The only two concepts likely to be new are:. The Map Source is the input Message Type. The Destination Schema is the Microsoft. Any Type. To access this Schema, you must have a Reference to Microsoft. The output of a Transform can be any content type in both an Orchestration and Port.
One thing to point here is that that this property seems to not handle relative paths too well. United States English. Post an article. Subscribe to Article RSS. Click Sign In to add the tip, solution, correction or comment that will help other users. Report inappropriate content using these instructions. GetPropertyValue property ;. MemoryStream ;.
Save stream ;. OwningContext ;. AddPart string. Empty, "Body" ;. LoadFrom stream ;. RefMessage this ;. AddPart part, name ;. RetrieveAs type ;. Addpart RequestMsg, "Requestpart" , "Addpartmessage" ;. String ;. RetrieveAs typeof XmlDocument ;. Load Stream messagPart. RetrieveAs typeof Stream ;.
0コメント