Thanks for the hint Alex.
It has been a good starting point at least for how to iterate over
Qooxdoo objects properties.
I was just missing some additional features that I needed to implement
in the helper class :
- keep some control on the properties that actually get transferred,
e.g. public wr
Hi Vincent,
On Friday 22 May 2009 Vincent Vandenschrick wrote:
> 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 o
Forget the question. I found a solution that consists in walking through
the Qooxdoo value object graph and transform them recursively into JS
untyped Object before sending them to the server. The reverse operation
is done when receiving the result. When hitting a qx.core.Object
descendant, onl
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 clas
