limweb / sabreamf

Automatically exported from code.google.com/p/sabreamf
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Unable to have a single object as argument with AMF3 #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
-- What steps will reproduce the problem?

1. Create a service method that receives an objet as argument, and prints it : 
public function test($obj) { print_r($obj); }
2. Call it with AMF3, with an object like {foo: "foo", bar:{baz: "bar"}}

-- What is the expected output? What do you see instead?

The printed thing is only the first property of the object ("foo"), whereas
it should be the full object.

-- What version of the product are you using? On what operating system?

Windows XP, SabreAMF 1.3

Original issue reported on code.google.com by thepurpl...@gmail.com on 1 Oct 2009 at 1:20

GoogleCodeExporter commented 9 years ago
I've just seen this issue has already been notified in Issue 13
http://code.google.com/p/sabreamf/issues/detail?id=13

Thus, a current workaround is to define a SABREAMF_AMF3_PRESERVE_ARGUMENTS 
constant
somewhere before processing AMF request (this feature is only available in the 
latest
SVN releases)

Original comment by thepurpl...@gmail.com on 1 Oct 2009 at 2:23

GoogleCodeExporter commented 9 years ago
This is correct. I'm marking this as duplicate

Original comment by evert...@gmail.com on 1 Oct 2009 at 2:26