访问PartyName上下文属性 [英] Accessing the PartyName context property

查看:130
本文介绍了访问PartyName上下文属性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


在行程中调用业务规则,并相应地应用转换。

我们如何访问PartyName上下文在ESB工具包2.0中使用它时,BRE中的属性?可以使用ESB.ContextInfo词汇表访问MessageType上下文属性。

谢谢,
Sumana。

推荐答案

非常好的问题!!!

我们遇到类似的情况,除了使用ESB开箱即用的默认值(OOB)之外,我们还需要访问其他上下文属性。为了解决这个问题,我们创建了一个自定义BRE解析器,它实际上将所有提升的属性复制到包含特殊getter / setter的自定义Dictionary类中。我们将此作为事实与OOB ESB Facts一起传递给Custom BRE Resolver,并根据这些新添加的事实创建了我们的规则。

换句话说,您必须插入context属性在BRE规则引擎中,默认情况下PartyName未插入BRE。您需要创建一个管道组件来执行此操作,使用自定义业务流程, 创建一个自定义BRE解析器,或创建一个从外部源获取其值的静态类。

如果我可以在代码plex上发布示例。

HTH
Very Good Question!!!

We have run into similar situations where we need to access other context properties besides the defaults that come out of the box (OOB) with ESB. To get around this we created a custom BRE Resolver that actually copied all of the promoted properites into a custom Dictionary Class which contains special getters/setters. We passed this into the Custom BRE Resolver as a fact along with the OOB ESB Facts, and created our rules based off of these newly added facts.

In otherwords, you'll have to insert the context property into the BRE Rules Engine, by default the PartyName is not inserted into the BRE. You'll either need to create a Pipeline Component to do this, use a custom Orchestration,  create a custom BRE Resolver, or create a static class that gets its value from an external source.

If I can I'll post the example on code plex or something.

HTH


这篇关于访问PartyName上下文属性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆