用于异步 bpel 流程中回调的 WS-Addressing ReplyTo
我有一个异步 bpel 进程,它调用客户端上的 cllback 服务来传输其响应。目前,我在相应的 wsdl 文件中静态定义了客户端的端点,一切正常。
现在我尝试让 ODE 不使用 WSDL 地址,而是从客户端的初始调用中提取replyTo 地址。我在初始调用中提供带有
的 WS-Addressing 标头。然而,这似乎不起作用。为了让 ODE 使用 ws-adressing 标头中指定的端点,我是否必须对流程进行任何更改?
编辑: 由于这似乎不起作用,我实现了一个解决方法:Apache-ODE 允许 BPEL 流程从任意 SOAP 标头读取数据。我使用此功能来读取所提供的
-header 的内容,并将其作为端点分配给 client-partnerlink。
I have an asynchronous bpel-processes that invokes a cllback-service on the client to transmit its response. At the moment, I statically defined the client's endpoint in the corresponding wsdl-file and everything works fine.
Now I am trying to have ODE not use the WSDL address, but to extract the replyTo address from the initial call from the client. I provide WS-Addressing headers with an <wsa:replyTo>
in the initial call. However, this doesn't seem to work. Do I have to make any changes to my process in order for ODE to use the endpoint specified in the ws-adressing headers?
Edit:
As this doesn't seem to work, I implemented a work-around: Apache-ODE allows BPEL-processes to read Data from arbitrary SOAP-headers. I used this feature to read the content of the provided <wsa:replyTo>
-header and assign it as endpoint to the client-partnerlink.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我是否正确理解您想要使用 WS-Addressing 来使用双通道绑定?目前官方 Apache ODE 版本不支持此功能,但已在路线图中。
Do I understand it correctly that you want to use a dual channel binding using WS-Addressing? This is currently not supported by the official Apache ODE builds but is on the roadmap.