> MyPanel.java
> public class MyPanel extends Panel {
> public MyPanel() {
> // THIS PANEL IS RECONSTRUCTED ON EACH MyPage REQUEST
> // BECAUSE MyPageTemplate DOES A new MyPanel...
> }
> }
>
> What could I do to use the old panel again?
Like Al hinted, you should not try to use the old panel again, but
instead focus on more fruitful forms of optimization. The construction
of Wicket components isn't very expensive in itself. What typically
makes it expensive is the data you expose through it, either using
models or directly. So what you should do is cache/ reuse the data
where you can, so that you avoid database round trips and other
expensive processing.
Often, the best thing to do when it comes to optimizing is to use a
profiler (YourKit for instance). Optimizing without using a profiler
to determine what the bottlenecks probably means you're optimizing the
wrong things.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
