|
Home > Archive > BizTalk Server Orchestration > April 2005 > Life of a Message with Orchestration
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 |
Life of a Message with Orchestration
|
|
| Don Keller 2005-04-27, 5:52 pm |
| In my orchestration a couple of message assignments and transforms are
performed. When I debug the orchestration the contents of a message only
seem to be available immediately following a step that creates a new message.
Performs 'forms" of the message prior to transformations, for example, only
have a null value later in the orchestration logic flow.
Shouldn't i still be able to refer to a message as it was received at the
original step in the orchestration, or is there really only one message
flowing through the orchestration that is getting transformed as it goes
along so it can only be viewed as it is at that given point in the flow of
the orchestration?
I can understand not being able to see a message until is has been assigned,
but it seems i should be able to look back at messages that had been
previously referenced in the orchestration.
Thanks for the input.
Don
| |
| Jon Flanders[MVP] 2005-04-28, 7:47 am |
| Don - messages are CLR variables - they get cleaned up at certain points
(either by being set to null by the orchestration code or being cleaned up
by the CLR's garbage collection) - that is why you see them as null later
in your orchestration
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"Don Keller" <DonKeller@discussions.microsoft.com> wrote in message
news:D417236E-4D01-45CC-BAF0-C6998FD5E077@microsoft.com...
> In my orchestration a couple of message assignments and transforms are
> performed. When I debug the orchestration the contents of a message only
> seem to be available immediately following a step that creates a new
> message.
> Performs 'forms" of the message prior to transformations, for example,
> only
> have a null value later in the orchestration logic flow.
>
> Shouldn't i still be able to refer to a message as it was received at the
> original step in the orchestration, or is there really only one message
> flowing through the orchestration that is getting transformed as it goes
> along so it can only be viewed as it is at that given point in the flow of
> the orchestration?
>
> I can understand not being able to see a message until is has been
> assigned,
> but it seems i should be able to look back at messages that had been
> previously referenced in the orchestration.
>
> Thanks for the input.
> Don
|
|
|
|
|