There are two possibilities: 1) In your application class add the following: mount(new HybridUrlCodingStrategy("/checkout", CheckoutPage.class));
2) If you have wicket-stuff annotation dependency (http://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation) you can annotate your page class with: @MountPath(path="/checkout") @MountHybrid public class CheckoutPage extends WebPage {} Alex V. Jenks wrote: > > Thanks Alex. > > I just had another meeting w/ the SEO guy today and the idea is to track > orders moving through our storefront in order go gauge sales based on the > SEO strategy. In other words, where did our customers come from (Google > search?), what did they buy, and did they make it all the way through the > checkout process. We need to be able to track pages in Google Analytics. > > If we could append/prepend some sort of value to the pages, while keeping > the dynamic Wicket page version parameter info in there, it would be > sufficient. In Analytics, the Wicket portion of the URL can be removed > and > the rest would be used to identify traffic moving through the site. > > Is HybridUrlCodingStrategy the way to go, with this in mind? Where are > some > good examples as to how to implement it and do what I'm describing? > > Thanks again! > > -v > > On Tue, Dec 1, 2009 at 6:04 AM, Alex Objelean > <alex_objel...@yahoo.com>wrote: > >> >> You can mount your page with HybridUrlCodingStrategy. This way, even >> session >> relative url's will be SEO friendly. >> >> But you must be aware of one thing, it makes sense to make SEO only >> bookmarkable pages (stateless pages). It is meaningless to make SEO aware >> session relative pages, because these will be shown as expired when >> somebody >> else will use these links. >> >> Regards, >> Alex Objelean >> >> >> V. Jenks wrote: >> > >> > I'm working on some changes for our storefront (Wicket 1.4, Java EE 5, >> > Glassfish 2.1) based on some recommendations made to us by an SEO >> > consultant. One of them is re-writing some of the URLs so as to have >> them >> > indexed by Google, etc. >> > >> > My concern is the Wicket WebSession that I use to pass around an >> instance >> > of >> > a stateful session bean. If I redirect to a mounted bookmarkable page >> > when >> > going through pages in the checkout process, vs redirecting to a new >> > instances of the page class, will there be any adverse effects on the >> > session? Will customers experience a problem with their shopping cart >> > sessions? >> > >> > Thanks! >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/%22Pretty%22-URLs-and-sessions-tp26581608p26591380.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- View this message in context: http://old.nabble.com/%22Pretty%22-URLs-and-sessions-tp26581608p26833349.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org