> My web app background is from page oriented frameworks, and now while > using wicket, I find myself creating pages over and over. > I think I can miss many of them, because most of the time all I do is > adding an intelligent reusable component to it.
I'm mostly using panels/ go for the smallest granularity I can get. We only really have a couple of pages, most of the navigation is done via replacing panels. Working like that takes a bit to get used to, but is great for avoiding code duplication. A page oriented approach is preferable for when you want pages to be bookmarkable or to be indexed by search engines. You can still do a lot with panels if you encode some logic in your URLs, but simply using pages might be a better idea. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
