ModalWindow with Page memory leak

in Page.writeObject (and sub-sequentially in Page.readObject)? Is it generally problematic to have field references to Pages in Components (or objects)? What would the most decoupled approach (object graph wise), thus minimizing serialization, be to implementing this? Thanks, Henrik Lundahl

Re: OutOfMemoryError (not PermGen) in PageSavingThread

Hi One thing you can check is if you have any references (instance variables, possibly implicit) to pages from your component hierarchy. That seems to cause memory leaks in the serialization. I reported a Jira issue about this yesterday (https://issues.apache.org/jira/browse/WICKET-1365).

Test failures due to incorrect order of attributes

(compared to the test case). Is this a known issue (on some platforms or configurations, possibly)? I couldn't find it in Jira. Regards, Henrik Lundahl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail

Re: Test failures due to incorrect order of attributes

Hi Thanks for clearing this out. I've filed https://issues.apache.org/jira/browse/WICKET-1389 on this. Regards, Henrik Lundahl 2008/3/1, James Carman [EMAIL PROTECTED]: Maybe it should use a TreeMap instead? On 3/1/08, Gerolf Seitz [EMAIL PROTECTED] wrote: Yes, this is a known issue