01-27-05 10:50 PM
Hi Sam,
I have run into the exact same problem in a project just completed, and in
trying to find a solution to the problem, I can across this blog post:
http://geekswithblogs.net/cyoung/articles/19546.aspx. Look at the section
titled Binding Ports Directly.
It seems as if an orchestration bound to a Direct port, where the "Partner
Orchestration Port" is MessageBox, the promoted properties, other than the
message type, are lost. To get around this, you can essentially need to
send the message through a pipeline for BizTalk to promote the properties.
This process and the options around it are discussed here:
http://geekswithblogs.net/gwiele/ar...1/10/14737.aspx
--
Kind Regards,
Nabeel Prior
Web: http://www.brainjar.co.za
Blog: http://www.brainjar.co.za/blog.aspx
"Sam Vanhoutte" <sam.vanhoutte@unilin.com> wrote in message
news:%23$nFuBJBFHA.2460@TK2MSFTNGP14.phx.gbl...
> Hello,
>
> I am facing this strange problem and I am totally stuck on it.
>
> I have a receive pipeline component that promotes values to the context of
> the incoming message (inmsg.context.promote(...)). I have an
> orchestration
> that has a receive shape bound to the port with the pipeline component.
> This receive shape has a filter on one of the promoted properties from my
> pipeline component. This property has the MessageContextPropertyBase as
> PropertySchemaBase.
>
> This filter works, so I am sure that the property is promoted.
>
> Now I am just sending this same message to the messagebox with a direct
> bound port. This port sends his message to another orchestration that has
> a
> correlation set running. At this point, I get a Routing Failure (no
> matching subscription found). If I look into the message details ->
> context, I can see all the properties, but they have all the IsPromoted
> column set to false!
>
> Why is the orchestration "unpromoting" all my properties?
>
> Best regards
>
>
[ Post a follow-up to this message ]
|