I am considering using Wicket to re-implement an existing (ageing, clunky
etc.) ordering application. My main concern is Wicket's ability to provide a
simple, (ideally configuration file based) mechanism for per-deployment
variation of the app for different countries.
The variation will come
Just make sure that the html elements with a wicket:id in the different
html versions have the same hierarchical structure. If you need to skip
some components for one language but not another it becomes a bit
harder. Then you'll actually need to add an invisible component for the
language in
