I've created a custom adapter that has several custom message context
properties created at my receive location.  The context properties are
visible in HAT and can be pulled back out of the message context on the send
side of things, so I think I have deployed them correctly.

The issue is, I'm not able to route messages based on these custom
properties.  Does anyone know of an additional step I need to perform before
I can route messages based on these properties?


Thanks in advance,

Alex

[ Post a follow-up to this message ]

To follow up the group, I ran across this post from Charles Young right
after posting to the group.

http://geekswithblogs.net/cyoung/articles/19546.aspx

There's a "promoted" boolean for each property, which I had assumed meant
that the property came from data, and should be false on my context
properties accordingly.  However, as per Charles, this is not the case.
This promoted boolean (which can be viewed from the message details page of
HAT) effects, at a minimum, whether the context property can be used in
subscriptions.

...that's what I get for not keeping up with the blogs I guess....

Alex


"Alexander West" <alexanderjwest@nospam.hotmail.com> wrote in message
news:uyFNuihCFHA.3928@TK2MSFTNGP15.phx.gbl...
> I've created a custom adapter that has several custom message context
> properties created at my receive location.  The context properties are
> visible in HAT and can be pulled back out of the message context on the
> send side of things, so I think I have deployed them correctly.
>
> The issue is, I'm not able to route messages based on these custom
> properties.  Does anyone know of an additional step I need to perform
> before I can route messages based on these properties?
>
>
> Thanks in advance,
>
> Alex
>

[ Post a follow-up to this message ]

huh, I thought I replied to this post hours ago...but my reply still isn't
showing up.

Anyhow, shortly after posting to the group, I came across this post by
Charles Young.  In it he states that there is a "promoted" field for all
promoted properties.  As he explains, I had assumed erroneously that this
field referred to whether the message property comes from a element or
attribute in a data schema, or is a separate message context property.   In
my case I'm dealing with the second, and so I thought "false" was a fine
value for these.  I was mistaken.  Charles claims that properties need to
have this value set to "true" for subscriptions to use them.

Here's a link to Charles' blog entry...
http://geekswithblogs.net/cyoung/articles/19546.aspx

I'll post back to the group with the results once I get to test it out....


Alex

"Alexander West" <alexanderjwest@nospam.hotmail.com> wrote in message
news:uyFNuihCFHA.3928@TK2MSFTNGP15.phx.gbl...
> I've created a custom adapter that has several custom message context
> properties created at my receive location.  The context properties are
> visible in HAT and can be pulled back out of the message context on the
> send side of things, so I think I have deployed them correctly.
>
> The issue is, I'm not able to route messages based on these custom
> properties.  Does anyone know of an additional step I need to perform
> before I can route messages based on these properties?
>
>
> Thanks in advance,
>
> Alex
>

[ Post a follow-up to this message ]

On the off chance that anybody's wondering how this turned out, I've posted
the results at....

http://www.caffedharma.com/tech/


Alex


"Alexander West" <alexanderjwest@nospam.hotmail.com> wrote in message
news:e3d5TuhCFHA.208@TK2MSFTNGP12.phx.gbl...
> To follow up the group, I ran across this post from Charles Young right
> after posting to the group.
>
> http://geekswithblogs.net/cyoung/articles/19546.aspx
>
> There's a "promoted" boolean for each property, which I had assumed meant
> that the property came from data, and should be false on my context
> properties accordingly.  However, as per Charles, this is not the case.
> This promoted boolean (which can be viewed from the message details page
> of HAT) effects, at a minimum, whether the context property can be used in
> subscriptions.
>
> ...that's what I get for not keeping up with the blogs I guess....
>
> Alex
>
>
> "Alexander West" <alexanderjwest@nospam.hotmail.com> wrote in message
> news:uyFNuihCFHA.3928@TK2MSFTNGP15.phx.gbl... 
>
>

[ Post a follow-up to this message ]