FLEX：期待 mx.messaging.messages.AcknowledgeMessage，但收到 null
将 RubyAMF 与 Flex 结合使用。
response = HashWithIn DifferentAccess.new( :handle_type => HandleType.first ) 工作正常，并且 HandleType 是我们 Rails 应用程序中的模型。
response = HashWithIn DifferentAccess.new( :user => User.first ) borks，我在 flex 中得到的响应是：
“本来期待 mx.messaging.messages.AcknowledgeMessage，但收到 null”
User 只是我们 Rails 应用程序中的另一个模型，但显然有一些不同之处。 ClassMapping 的设置相同，但具有正确的名称和属性。有什么想法可能导致它，或者寻找什么？我什至不能百分百确定我知道这个错误意味着什么。
任何帮助都会很棒！
Using RubyAMF with Flex.
response = HashWithIndifferentAccess.new( :handle_type => HandleType.first ) works fine, and HandleType is a model in our rails app.
response = HashWithIndifferentAccess.new( :user => User.first ) borks, and the response I get in flex is:
"Was expecting mx.messaging.messages.AcknowledgeMessage, but received null"
User is just another model in our rails app, but obviously there is something different about it. The ClassMapping is set up identically, but with the correct names and attributes. Any ideas what might be causing it, or what to look for? I am not even 100% sure I know what the fault means.
Any help would be great!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我想在这里问问题给了我解决这个问题所需的脑力：D
如果有人感兴趣，发生的事情如下：
在帐户价值对象（AccountVO）中，我有以下内容：
在用户价值对象（UserVO）中），我有以下内容：
所以，它基本上陷入了创建值对象的无限循环中，并且从未真正响应！哎哟！
I guess asking the question here gave me the necessary brain-power to solve this :D
In case anyone is interested, here is what happened:
In the Account Value Object (AccountVO), I had the following:
In the User Value Object (UserVO), I had the following:
So, it basically got stuck in an infinite loop of creating value objects, and never actually responded! Doh!