On 2010-08-09 18:18, Igor Vaynberg wrote:
it is not recommended to pass models between pages because if the
model is anonymous it can carry with it a reference to the other page
object and your session size will spike because your page also has a
reference to the previous page.
so no, it
there are provisions for serialization, but it is not perfect. eg if a
model alters a property of the page to which it carries the reference
those changes will be lost because what will be serialized is just a
reference to page x.
-igor
On Tue, Aug 10, 2010 at 12:14 AM, Leszek Gawron
On 2010-08-09 05:32, Igor Vaynberg wrote:
final Customer customer = item.getModelObject();
... Link link = new Link(link) {
public void onClick() {
setResponsePage(new CustomerPage(customer));
the line above holds
it is not recommended to pass models between pages because if the
model is anonymous it can carry with it a reference to the other page
object and your session size will spike because your page also has a
reference to the previous page.
so no, it shouldnt be that.
-igor
On Mon, Aug 9, 2010 at
I tried this, but still got the WicketNotSerializableException on the same
class - the JPA enhanced
version of my Customer object (which is a very simple bean). However, I tried
making Customer
serializable and now the exception is gone. I was thinking that I could not
make Customer
I have a DataView on a page to list items returned by a DB query (using JPA).
My database object
(Customer) has LoadableDetachableModel class (called DetachableCustomerModel)
that the provider
returns via the model() method. When populating the table, I want a link to a
page for the details
final Customer customer = item.getModelObject();
... Link link = new Link(link) {
public void onClick() {
setResponsePage(new CustomerPage(customer));
the line above holds on to the customer object, so the Link
