|
Home > Archive > BizTalk Server Orchestration > April 2005 > Understanding muti-part messages
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 |
Understanding muti-part messages
|
|
|
| Ok, I'm trying to get something straight in my head.
When I consume a web service in an orchestration and I go to create Message
variables to represent the request/response, when would I look in 'web
schemas' vs looking in 'multi-part message' types?
I think if the web service takes and/or returns a simple type, like a
string, then I would look under web schemas. If I was returning or taking an
object, that would be multi-part, correct?
Thanks.
STom
| |
| Jon Flanders[MVP] 2005-04-30, 6:07 pm |
| A multi-part message is a message wrapper around any message type. Instead
of using the message type directly - you are using it through a container.
The container can have 1 - N parts (i am sure there is a limit to N but I've
never tried to find it out). The nice thing about using MP Messages is that
if you change your underlying schema - you dont' have to change your Port
Types and Message Types. This is why I always use MP Messages.
When you using the "Add Web Reference" or use the "Add Generated Items - Add
Adapter" the code that runs always creates mutlipart messages types -
regardless of the underlying message schema type (whether is is simple like
string or a complex object/schema type).
When you are using the types generated by the "Add Web Refernce" the
designer places them under that special item in the tree view (when you do
things like create a message of a certain type) - but under the covers they
are really just Multi-Part Message Types.
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"STom" <stombiztalker@hotmail.com> wrote in message
news:eCCDoYbTFHA.2420@TK2MSFTNGP12.phx.gbl...
> Ok, I'm trying to get something straight in my head.
>
> When I consume a web service in an orchestration and I go to create
> Message variables to represent the request/response, when would I look in
> 'web schemas' vs looking in 'multi-part message' types?
>
> I think if the web service takes and/or returns a simple type, like a
> string, then I would look under web schemas. If I was returning or taking
> an object, that would be multi-part, correct?
>
> Thanks.
>
> STom
>
| |
|
| Ah, that makes a little more sense.
Now as an example, lets say I create a MP message type named "Request".
Under it, I create a message part named "ReqPart". I can then create an
orchestration message variable and point its message type to Request.
Now, if I go back to the Request type and want to add another message part,
lets call it ReqPart2, pointing to a different schema, how is this second
message part to be used? When I created my orch message variable, I just
pointed to Request, so how does it know to use ReqPart or ReqPart2? Just
trying to figure out here how to use N parts to a message.
Thanks!
"Jon Flanders[MVP]" <jon.flanders@gmail.com> wrote in message
news:uLSuTscTFHA.3140@TK2MSFTNGP14.phx.gbl...
>A multi-part message is a message wrapper around any message type. Instead
>of using the message type directly - you are using it through a container.
>The container can have 1 - N parts (i am sure there is a limit to N but
>I've never tried to find it out). The nice thing about using MP Messages
>is that if you change your underlying schema - you dont' have to change
>your Port Types and Message Types. This is why I always use MP Messages.
>
> When you using the "Add Web Reference" or use the "Add Generated Items -
> Add Adapter" the code that runs always creates mutlipart messages types -
> regardless of the underlying message schema type (whether is is simple
> like string or a complex object/schema type).
>
> When you are using the types generated by the "Add Web Refernce" the
> designer places them under that special item in the tree view (when you do
> things like create a message of a certain type) - but under the covers
> they are really just Multi-Part Message Types.
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "STom" <stombiztalker@hotmail.com> wrote in message
> news:eCCDoYbTFHA.2420@TK2MSFTNGP12.phx.gbl...
>
>
| |
| Jon Flanders[MVP] 2005-04-30, 8:54 pm |
| each of the parts appers on the variable that is the MP message. So:
Request.ReqPart
Request.ReqPart2
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"STom" <stombiztalker@hotmail.com> wrote in message
news:um11hkeTFHA.4056@TK2MSFTNGP15.phx.gbl...
> Ah, that makes a little more sense.
>
> Now as an example, lets say I create a MP message type named "Request".
> Under it, I create a message part named "ReqPart". I can then create an
> orchestration message variable and point its message type to Request.
>
> Now, if I go back to the Request type and want to add another message
> part, lets call it ReqPart2, pointing to a different schema, how is this
> second message part to be used? When I created my orch message variable, I
> just pointed to Request, so how does it know to use ReqPart or ReqPart2?
> Just trying to figure out here how to use N parts to a message.
>
> Thanks!
> "Jon Flanders[MVP]" <jon.flanders@gmail.com> wrote in message
> news:uLSuTscTFHA.3140@TK2MSFTNGP14.phx.gbl...
>
>
|
|
|
|
|