A wierd situation on chrome when dart_amf used about dart_amf HOT 6 OPEN

I fogot to comment that objects in server side were registerd with @Remote object in the client side

from dart_amf.

Does your deployed version on jboss work with Chromium 45 as well?

from dart_amf.

Yes, deployed version is workable with chromium45, but are fail on chrome50.
I tried to print out what I got after remote call, the instance(object) list was recieved by chromium, and the json objecct list was recieved. So interesting.

from dart_amf.

You will likely need to debug the names coming back and the names being registered when you use @RemoteClass

lib/src/amf_io.dart function readScriptObject

This function is where it decodes the incoming objects maybe uncomment the print statements and see what you can discover from that. Hopefully it is just a simple change to get it working for both.

from dart_amf.

Thanks for your suggestions. Something different were found when webapp executed on two browsers. Chromium would load the native dart script to execute, and chrome load the js code compiled by dart2js. The difference was observed by the dev tool. Furthermore, adopted your suggestios, l found maps for registered objects in amf_io will not keep my @RemoteObject, and only keep flex related class. So, I force to call registerClass to register my class in main, but when l used print to list all map, my clazz become meaningless alphabets, like {“com. mycompany.ws”, rj}, “rj” is the remote object “MyController”.

from dart_amf.

What is the name of the class it is looking for compared to the name you registered.

e.g. compare the output of https://github.com/blanchg/dart_amf/blob/master/lib/src/amf_io.dart#L621 with your code Amf.registerClass("server.package.Animal", Animal);

from dart_amf.