|
Home > Archive > BizTalk Server General > May 2005 > BizTalk 2004 :: Call Orchestration shape :: generic output?
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 :: Call Orchestration shape :: generic output?
|
|
|
|
Hello everyone,
I'm trying use the call orchestration shape that:
Accepts any xml document in (system.xml.xmldocument)
Searches for a specific node
If the node exits, processes it
replaces it in original document
Exits orchestration with updated document, still generic
(system.xml.xmldocument)
..... the problem is that he call shape seems to demand a strongly typed
document in response
Is there any way around this?
In addition to a orchestration parameter message of system.xml.xmldocument I
tried an "out" orchestration variable of system.xml.xmldocument with no luck
either
Any suggestions or a workaround?
BA
| |
| Jon Flanders[MVP] 2005-05-11, 2:48 am |
| I've done both before (had a send port using XmlDocument) and had an out
param of XmlDocument.
What kind of error are you getting?
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"BA" <biztalk.architect@gmail.com> wrote in message
news:4280d115$0$1359$5fc3050@dreader2.news.tiscali.nl...
>
> Hello everyone,
>
> I'm trying use the call orchestration shape that:
>
> Accepts any xml document in (system.xml.xmldocument)
>
> Searches for a specific node
>
> If the node exits, processes it
> replaces it in original document
>
> Exits orchestration with updated document, still generic
> (system.xml.xmldocument)
>
>
> .... the problem is that he call shape seems to demand a strongly typed
> document in response
>
> Is there any way around this?
>
> In addition to a orchestration parameter message of system.xml.xmldocument
> I tried an "out" orchestration variable of system.xml.xmldocument with no
> luck either
>
> Any suggestions or a workaround?
>
> BA
>
| |
|
|
Jon,
Requirements changed, so I didnt need anymore as of a change this morning so
I didnt reverse the strong type and try again.
I would imagine your experience (success) with generic output in a call
orchestration is more reliable since I discovered a bug inside the
orchestration which could have cascaded and made it seem the generic type
was the failure...
Onward ho
Thanks
BA
"Jon Flanders[MVP]" <jon.flanders@gmail.com> wrote in message
news:uLdvsNdVFHA.584@TK2MSFTNGP15.phx.gbl...
> I've done both before (had a send port using XmlDocument) and had an out
> param of XmlDocument.
>
> What kind of error are you getting?
>
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "BA" <biztalk.architect@gmail.com> wrote in message
> news:4280d115$0$1359$5fc3050@dreader2.news.tiscali.nl...
>
>
|
|
|
|
|