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 in most areas of the system, and while differences in the service layer aspects (validating a payment, calculating tax etc.) is currently handled using Spring, there will also be UI changes in page flow, content and field validation. As as simple example, if I understand correctly, Wicket will throw an exception if a component is declared in Java but not in the markup, so it doesn't look as though things could just be controlled using MyPage_en.html, MyPage_fr.html etc. Apologies if I missed something simple here, I'm very keen to use Wicket, and I'm hoping that the per-deployment issue is not going to force me down the 'XML config hell' route of Struts etc. Thanks Peter -- View this message in context: http://www.nabble.com/Per-Deployment-Variation-tp14731151p14731151.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]
