On Wed, Aug 13, 2008 at 6:13 PM, Nick Heudecker <[EMAIL PROTECTED]>wrote:
> Why did you move away from Seam? It was a project for one of our clients. They let us pick the technology. We first selected SEAM because we thought it would be easier for the client to take over the code once the app would switch to maintenance mode (JSF is a standard, wicket is still an obscure framework, yadayadayada...). We developed the first 75% with SEAM. Everything worked great (functionally speaking), the client was happy, but the code was hard to follow (xml config files, triggers, etc.), the compile/test cycles were very long, the project structure was too complex (we use maven: we needed 3 different modules to produce the final ear file). So, without telling the customer (and without charging them) we ported the project to wicket. Huge win: - Simpler code - shorter compile/test cycle (with wicket we're launching the app with embedded jetty during development) - shorted learning curve: it's easier to bring a developer up to speed on a wicket project that it is on a jboss/seam one. - amazing support through the form I'm not saying SEAM is a bad framework. It might even be better than Wicket, or better suited for some environments. But one thing is certain: it's a lot more complex to master. > > On Wed, Aug 13, 2008 at 5:59 PM, Toto Laricot <[EMAIL PROTECTED] > >wrote: > > > We ported an application from JBOSS/SEAM to Wicket in 2 weeks. The app > has > > been successfully deployed in production. > > Although the wiki had all the scode sample we could wish for, and > searching > > the forum always answered our questions, I'll buy the book to express our > > gratitude to the Wicket team. > > It's been an awesome experience. > > T. > > On Wed, Aug 13, 2008 at 4:21 PM, Gabriel Bucher < > [EMAIL PROTECTED] > > >wrote: > > > > >
