All the "Crawlable"/"indexable"/Search Engine friendly pages cannot be session relative. Inherently those are more secure pages, probably better used for secure portion of your application vs. freely crawlable. Besides Search engines dont seem to like session ids. One can still achieve the effect of session relative pages for bookmarkable pages by using appropriate models and/or caching.
My 2 cents... Mathias P.W Nilsson wrote: > > Hi! > > When building a site for a customer with wicket one of the nicest thing is > that you can create a page and pass objects, Arrays etc to the page > constructor. I use this on almost every page. > > List<ItemFilter> filters = new LinkedList<ItemFilter>(); > > filters.add( new BrandFilter( new Brand( 12 ) ) ); > filters.add( new OutletFilter( false ) ); > filters.add( new GenderFilter( Gender.FEMALE ) ) ; > ..... > setResponsePage( new ItemPage( filters ) ); > > Now, If I should use PageParameters for this and remain the query in the > PageParameters I would have a difficult time to parse this. When Using the > PageNavigator I would get in even more trouble. > > My question is. How do you get around this if the customer requires the > site to be google friendly and you still want to use a stateful approach? > Is there some other way of letting wicket take care of the state and still > have google friendly sites without using PageParameters? > > SiteMaps? > Static pages? > > Has anyone experienced the same problem? > -- View this message in context: http://www.nabble.com/Google-friendly-site-remaining-wickets-nice-stateful-page-contructor-tp18981499p19039481.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
