Another approach might be to wrap the various Link classes to log when pages are accessed. Cumbersome if you don't already have Link subclasses - which we do for access control.
I'm not familiar enough with the Wicket internals. Maybe there's something easier.
On 5/18/06, Frank Silbermann <
[EMAIL PROTECTED]> wrote:
If all the pages in my Wicket application extend a common base page, what are some of the ways I could keep track of the each page's popularity? I'm thinking of something I could put on the base page that, upon construction, would identify the actual subclass being constructed and add it to that class' counter in persistent storage.
Have any of you done something like this? If so, how did you architect that capability?
