Re: [Wicket-user] Component#getSizeInBytes() and internal classes

2006-01-24 Thread Sven Meier
Ok, maybe I wasn't clear enough with my description: The current display of component sizes on the error page is bogus. Many component instances are based on anonymous inner classes and have a reference to their enclosing component. If asked for their size they'll always include the size of the

Re: [Wicket-user] Component#getSizeInBytes() and internal classes

2006-01-24 Thread Igor Vaynberg
the reason its set to null is that when it is serialized into session most likely the parent would have already been serialized and thus it would just be a reference and not a another full serialized version. so this function gives an accurate representation of this component /in session/. -IgorOn

Re: [Wicket-user] Component#getSizeInBytes() and internal classes

2006-01-24 Thread Johan Compagner
If you want to calculated the model size then yes that is the full size of the model. (so including the parent)because that is how it gets serialized anyway (in session and in model cloning)And what is the parent? You now just say component.getParent()But that doesn't have to be the one of the anon

[Wicket-user] Component#getSizeInBytes() and internal classes

2006-01-24 Thread sven
Sorry if this has been discussed before (or if I'm completely wrong on this): It seems that Component#getSizeInBytes() gives wrong results in case of non-static nested classes (which is quite common in Wicket): >public LoginPage() { > add(new Link("login") { >public void onClick() { >