does wicket still have troubles with restful URLs? On Thu, Feb 16, 2012 at 12:49 AM, Lenny P <[email protected]> wrote: > -1 for Wicket. > We did a web framework bake-off and wicket lost for 2 reasons: > designer friendliness (lack thereof) and violation of the DRY > principle. > (see > http://groups.google.com/group/javaposse/browse_thread/thread/5a133dc17ca63462 > ) > We are now using Tapestry with Glassfish with both Java and Groovy > page classes > and it is working wonders! > > On Feb 10, 9:33 am, Casper Bang <[email protected]> wrote: >> +1 for Wicket. While still statefull, infinitely better than ivory tower >> JSF. Easy to create and reuse components and integrate with templates. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. >
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
