|
Home > Archive > BizTalk Server Orchestration > April 2004 > BizTalk 2004 Orchestration | System.Xml.XmlDocument
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk 2004 Orchestration | System.Xml.XmlDocument
|
|
| Sachin Surana 2004-02-08, 8:42 am |
| Hi All,
We are using BizTalk 2004 and we require to call (from
orchestration) a .NET component which takes
System.Xml.XMLDocument as an input.
How do we convert a Message in Orchestration to
System.XML.XMLDocument ?
Thanks in advance.
Regards,
Sachin
| |
| Delfin Heras 2004-02-25, 3:35 pm |
| In Biztalk 2002 a message is string, then you can create a com object that
takes a string which is an xml as a parameter...
unless orchestration messages in biztalk 2004 are not strings anymore, that
should work for you
"Sachin Surana" <sachinsurana@hotmail.com> wrote in message
news:a77b01c3ebed$e6844330$a001280a@phx.gbl...
> Hi All,
>
> We are using BizTalk 2004 and we require to call (from
> orchestration) a .NET component which takes
> System.Xml.XMLDocument as an input.
>
> How do we convert a Message in Orchestration to
> System.XML.XMLDocument ?
>
> Thanks in advance.
>
> Regards,
> Sachin
>
| |
| Ivan Ho 2004-04-29, 3:37 pm |
| The MessagePart of the Message should be in System.Xml.XMLDocument. So
instead of defining your message directly in SchemaType, you may want to
create a Biztalk MessageType and then in your MessageType messagePart set
the type to a schema. Now you can do this within your expression editor:
SomeDotNetComp(Message1.MessagePart_1);
Thanks,
Ivan
--------------------[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
|
|
|
|
|