> This is obviouly a huge performance issue. I wonder if it is. Java is optimized for creating objects, and creating new ones is often cheaper than reusing old ones if you take synchronization and lookups into account.
Are you sure it is a bottleneck? If you haven't seen any actual performance problems (and determined that it is the web tier causing it, which is often unlikely given that accessing the back-end such as databases often take the majority of the processing of a request) you'd be wasting your time. Premature optimization is evil :-) If you're still unconvinced, take a look at org.apache.wicket.examples.staticpages in wicket-examples; it might do what you want. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
