Hi all, I've defined a complete class hierarchy of value objects that need to be exchanged with a Java backend through Qooxdoo RPC.
This implies, for service method parameters: -> transforming JS objects to JSON and then to their equivalent Java beans instances on the server with automatic class hinting (JS objects class names match Java beans class names with default contructors, and so on...); I've overriden the "resolveClassHint" method of RemoteCallUtils to achieve this. -> doing it also the reverse way with automatic client side class hinting; I've overriden the "filter" method of RemoteCallUtils to include a "class" property to each transfered JSON structure so that it can be leveraged on the client side to construct their equivalent JS object. All the JS value objects inherit (even indirectly) from qx.core.Object to leverage properties, event handling, .... The first shot ended up with a "too much recusion" JS error. Debugging the execution code shows that all the value object members are recrusively serialized to JSON, and qx.core.Object holds a lot ;-) So, here is the question : What is the best way to plug-in a custom JSON serialization/de-serialization strategy on the client side ? It seems that the qx.util.Json static class is responsible for this but I don't have a clue on how to cleanly override its default behavior. Thanks for any hint. Regards, Vincent -- Vincent Vandenschrick Jspresso Framework http://www.jspresso.org ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
