Jeff, I will try to do better on the documentation and examples, but I think the tests are quite useful if you would like to see how the components work.
Best regards, Joachim On Tue, 2010-02-23 at 09:46 -0600, Jeffrey Schneller wrote: > Joachim, > > > > Thanks for this information. It shows that we made the right choice with > Wicket for a new retail site. Also thank you for posting your components as > open source. Do you have any examples of how these components can and should > be used. In particular the jofilter, wicket-stateless, and expiring-cache. > > > > Thanks. > > > > Jeff > > > > > > From: Joachim F. Kainz [mailto:j...@jolira.com] > Sent: Monday, February 22, 2010 12:05 PM > To: users@wicket.apache.org > Subject: Wicket used for mobile.walmart.com > > > > Fellow Wicket Users, > > The question if Wicket is suitable for large enterprises has just become > easier to answer: The largest enterprise in the world is now using Wicket for > its mobile site. Check out mobile.walmart.com (or just point your mobile > phone to www.walmart.com and get redirected automatically). > > The reason why my client decided to go with Wicket makes it easy to support > multiple different types of devices. The walmart mobile application supports > different HTML for three categories of devices (L1: iPhones & challengers, > L2: BlackBerries, L3: Plain Old Devices). These three experiences are > supported by the same Java code on the server side. > > We added a few components to Wicket, mostly because in the retail arena being > stateless is very important. Our components are available at > http://code.google.com/p/jolira-tools/. > <http://code.google.com/p/jolira-tools/> > > Wicket is an awesome product and I would like to thank the Wicket team for > all there work. One day I hope to get the largest enterprise in the world to > donate an appropriate amount of money for future development! :) > > Best regards, > > Joachim > > http://www.jolira.com > > > >
