Link to the "binary" jar file added : no need to checkout or compile.
Check http://qooxdoo.org/contrib/project/rpcjavapojo
On 18 mai 2010, at 08:26, Jean-Baptiste BRIAUD -- Novlog wrote:
> All users of previous unofficial version are strongly encouraged to migrate
> to the current version.
> Two important bugs had been corrected and a programming hook had been added.
>
> Currently, you have to checkout and run the jar target of the ant build.
>
> As soon as I can I'll add the jar file accessible somewhere (in the wiki ?)
> to avoid that no added value work for contrib users.
>
> On 15 mai 2010, at 13:49, Jean-Baptiste BRIAUD -- Novlog wrote:
>
>> Hi,
>>
>> Novlog is proud to announce that new contrib is now available on Qooxdoo SVN
>> contrib.
>>
>> the name was quite hard to choose : Rpc<XXX><YYY> was the pattern choosen by
>> Qooxdoo for backend where :
>> XXX : is the backend techno, here Java
>> YYY : something specific for that implementation compared to RpcJava witch
>> is the default historic implementation.
>> Here POJO stand for Plain Old Java Object. That mean we are using just
>> classical simple Java classes as business object that goes from and to
>> client side.
>> In the current RpcJava implementation, the name should be RpcJavaBean
>> (YYY=bean) to explain that it rely on JavaBean standard => getter/setter are
>> mandatory.
>>
>> RpcJavaPojo contrib is a Java backend implementation that is compatible with
>> current RpcJava contrib.
>> The contrib is composed of 2 modules :
>> * serialization. It use JSON to serialize Java objects, just like RpcJava
>> including the "date hack". Serialization use code from json.org.
>> * RPC : it use the qooxdoo serialization standard {service, method, param}
>> just like RpcJava contrib.
>>
>> There are few differences from RpcJava :
>> * simpler (but is may be a question of point of view) : works at attribute
>> level rather than getter/setter level. Less code is necessary since
>> getter/setter are not used.
>> * more standard : rely on Java keyword transient to tell an attribute should
>> not be serialized
>> * more modular : RPC and serialization are clearly separated
>> * more flexible : there are more programming hook (maybe still not enough)
>> to take the control at different step of both RPC and serialization
>> * quicker : 2 times faster based on a simple manual stopwatch
>> * more up to date : using Java 6 (Java 5 is a minimum) with generics, ...
>> but this doesn't change your life when you're just using it ;-)
>>
>> To checkout the contrib : svn co
>> https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/RpcJavaPojo/trunk
>> RpcJavaPojo
>>
>> The only doc is currently the readme.txt file and few emails on the mailling
>> list.
>>
>> Feel free to ask question here, try it, propose modification, ... open
>> source spirit !
>>
>> Enjoy,
>>
>> JBB.
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
