Wicket's markup is clear and intuitive for people with web skills, but a Wicket application's presentation logic is written in Java, not mark-up. Someone with weak understanding of object-oriented design and programming (e.g., someone whose web skills are based on tools like ASP/VB-6 or Cold Fusion) will not be able to make the best use of the Wicket approach, and may even have trouble learning the framework.
It may get easier for such people to learn Wicket when textbooks reach the market, but for now I occasionally had to resort to reading the object-oriented Wicket implementation code. (For example, my problem required me to subclass DataTable. To figure out how to do this I had to study the code behind DefaultDataTable -- a wicket-provided subclass that didn't solve my problem, but whose implementation illustrated the kinds of things I needed to do in my own subclass). If you can use Wicket, I'd recommend doing so. Compared with the ASP.NET application I'm rewriting, my code-base is about one-fourth the size (mainly because Wicket made it much easier to abstract fragments of presentation logic, appearing with minor variations on page after page, into my own reusable components). The tag-files generated by ASP.NET were huge compared to the little ones I had to write with Wicket, though to be fair, I had to write my tag files whereas the ASP.NET tagfiles were generated by the IDE. On the other hand, I didn't have to keep drag-dropping the same patterns of components onto page after page as did the ASP.NET developer. (I imagine that JSF programming is very similar to ASP.NET programming -- but without the benefit of so powerful an IDE.) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Bate Sent: Thursday, June 22, 2006 9:47 AM To: [email protected] Subject: [Wicket-user] Is Wicket ok for DDA web applications? Hi, I'm considering looking at Wicket after a painful two weeks on JSF (actually Apache MyFaces) and thinking "there has to be a better way"...!. Most of my work over the last 5 years has been JSP/Struts etc... I'm a J2EE developer but coming firmly from the web side rather than a back-end developmer. I want to use a framework that has clean markup and is intuitive for people with web skills. (Anyone who has seen the ghastly JSF tabular layouts and poor Tomahawk div implementation will understand!) I am about to start work on a webapp where one of the requirements is for a DDA compliant interface. If I were to use Wicket, does it have any reliance on Javascript or anything else that may jeopardise a DDA interface? Thanks, Andrew Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
