> When my portal is online, I will publish some aspects or even a large part of > this as constribution. I think that in the next time I will get some > problems with instances and memory management. As I have seen, Wicket creates > a lot of new Instances for each page visit, but this seems to be a solvable > by design of my application.
I wouldn't be worried about creating many objects. That's exactly what hotspot is optimized for. Memory management is something you should be aware of when coding with Wicket. It's our catch/ tradeoff, though it isn't as much of a problem necessarily for most cases. We've had multiple discussions on this, including tweaking options etc, so if you search a bit in the mail archives (http://www.nabble.com/Wicket-f13974.html), you'd find a good read. Also, Wicket 2.0 has more optimizations in this field then the current Wicket 1.2. Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
