WCF-WebHttp适配器上的可变映射提升了大于255个字符的属性 [英] Varible Mapping on WCF-WebHttp adapter promoted property large than 255 chars

问题描述

我们使用双向发送端口来调用REST API。

适配器是WCF-WebHttp，而在BtsHttpUrlMapping中我们有一个名为的变量id，如下所示：
$


< BtsHttpUrlMapping>

 < Operation Method =" GET"地址="对象ID = {ID}"？; />
$
< / BtsHttpUrlMapping>



然后在Varible Mapping中我们指定一个包含消息中所有ID的提升属性。

这个工作正常，直到我们收到一条大邮件，并且提升的属性大到256个字符。



错误信息：详细信息：" ;提升属性的值不能超过256个字符。



有关如何解决此问题的任何消息？我们对REST API没有任何影响。



/ Ulrik

Hi,
we using a two-way send port to call a REST API.
The adapter is WCF-WebHttp and in the BtsHttpUrlMapping we have a variable named id, like this:

<BtsHttpUrlMapping>
 <Operation Method="GET" Url="Object?ids={id}" />
</BtsHttpUrlMapping>

and then in Varible Mapping we specify a promoted property which contains all ids from the message.
This works fine, until we received a large message and the promoted property got large then 256 characters.

Error message: Details:"The value of a promoted property cannot exceed 256 characters.

Any sugestions on how to solve this? We have no influence on the REST API.

/Ulrik

推荐答案

首先，尝试常规的上下文属性，而不是提升。 我只是不记得常规属性是否适用于URL映射。

First, try a regular Context Property, not Promoted.  I just don't remember if regular properties will work in the URL mapping.

推广属性限制无法解决。 从开始就是256.

There is no way around the Promoted Property limit.  It's been 256 since the beginning.

你的后备选项是使用常规的Context属性，然后在行为中修改URL。

You fallback option is to use a regular Context Property, then modify the URL in a Behavior.

虽然有他们没有错，很长的网址只是糟糕的设计。 我仍然向你的管理层解释这是API的问题。

While there's nothing wrong with them, very long urls are just crappy design.  I'd still explain to your management that it's the API's problem.

这篇关于WCF-WebHttp适配器上的可变映射提升了大于255个字符的属性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！