Thanks. I looked that source of the staticpages examples and even more troubled with it. It generates each static links via a costly markup object creation and attribute modification. In a base template page that may contain,say 50 such links, that would be displayed for all site (bookmarkable) pages, it would mean a lot of object creation/destruction just for a static markup. I saw a post about running out of wicket memory during stress test. I had quite a few times noticing the turnaround is quite slow in my app even though it is just a page with many constructed links, even though I do not have test suite to back it up.
Would it be possible to turn a bookmarkale/stateless page object into a stateful page during a session once user first access it. After all, bookmarkable page link is for accessing the page when you return to it after ,say a few days. Once you access/create it, during the session, it should be considered a stateful. >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
