I must also say that in our company the popularity of wicket is growing up. We completed at least 3 small-medium sized projects using Wicket. There is another project in progress and few prospects. Number of developers who had a contact with wicket grew from 1 to 5 developers. It is not very much, but it is still a progress. Any time the client give us a freedom to choose a technology, Wicket is our first option. But, usually client chooses the technology... and most of the time it is JSF. This happening because the wicket, besides not being a "standard" technology, suffers from marketability related statistics and is not so popular between developers.
Alex Objelean wrote: > > For the last 7 months I was working on a project using JSF (Icefaces). It > indeed have nice features, but still it does not compare at all with > Wicket (easy of componet development, flexibility, testability, etc, etc). > > I do love wicket, but I must agree that "... corporations still prefer > JSF". Big players preffer "the standard framework", it is still their > strong point. Maybe it is all about marketing? > > > -- View this message in context: http://www.nabble.com/%22This-time-last-year%22-....-is-Wicket-really-a-disappointment--tp18608440p18609155.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]
