|
Home > Archive > BizTalk Server General > May 2006 > custom message context property
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 |
custom message context property
|
|
| Stefan 2006-05-29, 5:21 pm |
| I would like to pass some message specific args along with the message
through a custom send pipeline, but the arguments are not part of the
original message. I figured i would have to use message context properties
but i'm not really sure how.
Is there a way to add message context properties from an orchestration so
that they are accessible from a custom pipeline component?
| |
| Tomas Restrepo \(MVP\) 2006-05-29, 5:21 pm |
| Stefan,
>I would like to pass some message specific args along with the message
> through a custom send pipeline, but the arguments are not part of the
> original message. I figured i would have to use message context properties
> but i'm not really sure how.
Yep, those are the ones you want to use. Make sure you define them in your
property schema as being of MessageContextPropertyBase type (instead of
MessageDataPropertyBase type).
> Is there a way to add message context properties from an orchestration so
> that they are accessible from a custom pipeline component?
Sure, just add them to the message context during message construction in a
Message Assignment shape, using the syntax:
MyMessage(<Property> ) = <value>;
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| Stefan 2006-05-29, 5:21 pm |
| I created a property scema with the property "thumbprint" as a
"MessageContextProperty". However, when i try to do
MyMessage(thumbprint) = "foo";
i get a message saying that the identifer "thumbprint" doesn't exsist.
The property schema is in the same project as all my other schemas, so
references should be correct. What am i missing?
"Tomas Restrepo (MVP)" wrote:
> Stefan,
>
>
> Yep, those are the ones you want to use. Make sure you define them in your
> property schema as being of MessageContextPropertyBase type (instead of
> MessageDataPropertyBase type).
>
>
> Sure, just add them to the message context during message construction in a
> Message Assignment shape, using the syntax:
>
> MyMessage(<Property> ) = <value>;
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2006-05-29, 5:21 pm |
| Stefan,
>I created a property scema with the property "thumbprint" as a
> "MessageContextProperty". However, when i try to do
>
> MyMessage(thumbprint) = "foo";
>
> i get a message saying that the identifer "thumbprint" doesn't exsist.
> The property schema is in the same project as all my other schemas, so
> references should be correct. What am i missing?
You're missing the namespace/typename. Remeber that all schemas have a
typename associated with them (which is part of the .xsd file properties),
which in turns gets a namespace when compiled by the biztalk project. You
need to use the fully qualified name of the property
(for example: MyPropertySchema.Thumbprint, or
Winterdom.Schemas.AdapterProperties.Thumbprint).
Check your schema settings and you should be able to find it.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
|
|
|
|
|