Everyone, thanks for the help. I finally found the problem by debugging
into componentModelChanging as several people had urged me to do. The
memory hog was an object I had in the data provider, which was a member
class of my Page class. I wasn't using the page in it, but it still had
compiler generated references to the page object. Therefore, it was huge.
Seems like a pretty easy trap to fall into; if a view object sneaks into
a model somehow, your session is headed for disaster. Wouldn't that mean
you can never have an anonymous subclass of Model in any kind of
Component? I feel like I've seen that all over the place.
Nathan
Phil Kulak wrote:
Are you using a model now and doing the lookup there? If you just
downloaded the new code and didn't change you code to use the new API,
nothing will change. I made it all backwards compatible.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
