RE: [Wicket-develop] should we make AbstractResource serializeable or not?

Tue, 08 Mar 2005 07:14:55 -0800

Ok.. I must have done something wrong, because I had a list of objects (that weren’t serializable) in a detachable pageable list model, and I was receiving an exception saying that it wasn’t serializable.

 

How does the case work where I bind the elements in the list to more components.  I presume that I would have to wrap each of them in a detachable model too ?  This is probably where I have gone wrong.

 

For example..

 

Say I have a list of ContactEntity objects (hibernate mapped pojos)

I have a detablable pageable list model of contacts (using a hibernate query and storing the criteria as a non transient property of the list model)

Then to make a grid editor, I bind properties of each contact to TextField inputs.  

Would I need to make a detachable contact model that loads the contact by id and bind it to the form components ?

 

Thanks,

 

Cameron.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Johan Compagner
Sent: Wednesday, 9 March 2005 12:49 AM
To: [email protected]
Subject: Re: [Wicket-develop] should we make AbstractResource serializeable or not?

 

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