Johan,

You do not have to have a default constructor or any other condition. See http://xstream.codehaus.org/ for more information. That's the beauty of XStream. Is there a way for us to take over serialization from the web container and do it ourselves?

Gili

--Original Message Text---
From: Johan Compagner
Date: Tue, 08 Mar 2005 16:42:16 +0100

again
We don't handle the serialization that is something the webcontainer does

And i don't really like xml serialization. Because it always means you have to have a default constructor for serialization
Maybe there is an approache that doesn't need this but as far as i have seen now a xml serialization always uses a default instance (That it creates)
to see the differences between a default object and the object to serialize.
That could be pretty heavy. And all models must have a default constructor and be able to handle a that.

Gili wrote:
Again coming back to this point: why are we not using XStream that allows us to handle everything automagically?

Gili

--Original Message Text---
From: Johan Compagner
Date: Tue, 08 Mar 2005 15:49:18 +0100

because the model itself will still be serialized.
A detachable model doesn't mean the model itself is detached but the developer can detach the contents.

For example if you have a heavy weight component in your model that you can relookup from somewhere
by an ID. Then in the detach you store that id in a non transient instance reference. And youre heavy weight object
is cleared or hold only in a transient reference.

Then when the component and its model are serialized only the id is serialized with the model not youre complete object.

johan


Cameron Braid wrote: Speaking about serializable stuff...

With detachable models, why do they also have to be serializable ?

Cameron.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:wicket-develop-
[EMAIL PROTECTED] On Behalf Of Johan Compagner
Sent: Wednesday, 9 March 2005 12:28 AM
To: Wicket Developer List
Subject: [Wicket-develop] should we make AbstractResource serializeable or
not?

Our clone by serialize did encounter a few serialization exceptions for
example
all the Resources (like image). Should we make AbstractResource
serializeable?
those can be in the session..

johan




-------------------------------------------------------
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




-------------------------------------------------------
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







Reply via email to