Hi Piotr, right! I think we still have something wrong. Let me explain: I'm right now trying to make a first communication with our company app. I get to communicate from Royale to Java sending a populate type object, but I'm still don't get the response ok, I'm getting a "Failed decoding the response". The object coming is very complex, but I think all the pieces coming in that object are currently working. So I'm trying to understand what's failing. So while the example works with something similar, in my current app still don't have it. I must say we have many other things in the mix like security filters and had to remove a especial handling of RemoteObjects we have in place to start from a minimal scenario.
Maybe if you try with PHP, you'll find some problem. I think we are mostly done, and maybe the problem is not in Royale but in how configuration is done in our respective projects. Good luck with your experiment! :) Carlos 2018-05-16 12:08 GMT+02:00 Piotr Zarzycki <[email protected]>: > Hi Carlos, > > I'm wondering now what should be on the AMF PHP sight to have it working. > Maybe I will try to find some time to investigate it. Since on Java HashSet > is ok, maybe on PHP sight there is something which can accept ArrayList. ;) > > Thanks, Piotr > > 2018-05-16 12:02 GMT+02:00 Carlos Rovira <[email protected]>: > > > Hi, > > > > just let you know that I tried to retrieve a Collection from Java with > > RemoteObject/AMF, and that worked without problem. I updated the example > > with this test that compose a java.util.Set (a HashSet), send it and we > get > > it in Royale as a royale ArrayList. > > > > I'm a bit surprised that this works without much problem. Still don't try > > (know) if sending ArrayList from Royale to the backend will work. Maybe > > BlazeDS expect to find an ArrayCollection, and will find an ArrayList... > > > > So far so good. I completed the example as well with some more > combinations > > (nesting typed objects in a typed object, nesting an array of > objects,...). > > > > As well fix a problem in Reflection adding a Try-Catch, that make object > in > > both layers need to have exactly the same number of properties. Now, the > > as3 layer can have less properties. This is something widely use in Flex. > > > > thanks > > > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* > -- Carlos Rovira http://about.me/carlosrovira
