Hi all,
I've built a Java and Qooxdoo class library that maps [almost] any Java
objects seamlessly between the client and server object models without
requiring extra plumbing code to be written; I think it's interesting and
possibly a successor to the Java RPC contrib but first I want to ask for
comments and feedback to see if anyone else agrees. If there's interest
I'll submit it.
In brief summary, it uses reflection to replicate the interface hierarchy
and generates matching proxy stubs on the client, and tracks those object
instances between client and the server so that:
a) you can expose virtually any arbitrary server object to the client;
b) marshalling of complex objects is possible without special plumbing -
E.G. you can get an object from the server and later on pass it as a
parameter to another server object method call;
c) POJOs beans and other standard Java data structures map automatically to
JSON, and client JS arrays and objects map to Collections, arrays and Maps
on the server (the JSON marshalling is done by Jackson at
http://jackson.codehaus.org/).
There's documentation, junit tests and example code at
http://www.zenesis.com/qrjo.html.
Included in the proposal (see docs) is a simple idea to define properties in
the Java classes so that property values can be synchronized between client
and server in batch (i.e. only when necessary), which (with a few minor
patches to Qooxdoo properties) could allow objects created on the client to
be proxied or copied to the server, i.e. reverse proxying.
John
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
