On Wed, 02 Mar 2005 11:10:37 -0800, Jonathan Locke wrote:
>nifty. maybe we could write our own serialization to make cloning
>faster... and when i say "we" i mean someone other than me... ;-)
>
>Gili wrote:
>
>> For serialization, use XStream. There is nothing thorny about
>>it (no configuration needed), in exchange for a performance drop.
I think you guys should read
http://xstream.codehaus.org/index.html
Their goals are very much in line with Wicket's. They trade a
bit of performance for huge benefits in ease of use.
Here is how you serialize an object graph to XML:
String xml = xstream.toXML(myObject);
That is all. The object doesn't have to be serializable. You
don't need to do any special mapping or configuration. It just works.
Personally, I feel that dropping normal serialization in favour
of XStream is a *huge* step forward. Sorta like moving from C to Java.
Is there a way for us to use non-serializable objects with the
underlying web container? Can't we do serialization on its behalf and
leave it out of the loop?
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
