Well as a Java developer, I find it cool that I can continue to apply best-practice OO design and utilize my IDE to the fullest. If you have some common header, login form or whatever you can easily encapsulate this as a component (well as best as you can represent a component in Java) and obtain re-usability too. Contrasted to JSF/Facelets which is supposedly also a component technology, I just find Wicket so much simpler and there's no need to do iteration, branching etc. in XML or remember which tags nests/composes well and which don't. With Wicket you can even give your HTML template to a designer and the custom wicket tags will just be ignored by the designers WYSIWYG tool.
Bottom line, I don't like the magic introduced by many of the frameworks if I can have a clean and simple (type-safe) Java API to explore through my favorite IDE. /Casper On 26 Sep., 17:42, phil swenson <[email protected]> wrote: > could you give some examples as to what is cool about wicket? > > On Sep 26, 4:36 am, Casper Bang <[email protected]> wrote: > > > Wicket (for wide-spectred Internet solutions) or GWT (for targeted > > intranet or high-interactivity solutions) for me. The only ones that > > deliver rather than being some ivory tower experiment. > > > /Casper > > > On 25 Sep., 21:25, CKoerner <[email protected]> wrote: > > > > I'm curious on what people feel are the top 3 Java based web > > > frameworks. You can round it out with 2 honorable mentions if > > > desired. > > > > Thoughts? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
