Hi Frank, > I'm working alone, and > have a lot of freedom in the tools and frameworks I choose.
That's the best job :) > Wicket sounds like a good approach – said to be easier to learn and use than > JSP/Struts or JSF; and I could cannibalize the html generated by the ASP.NET > pages, insert Wicket id attributes, and then work mostly with what I know > best – POJOs. Do you think this is a good approach? Sure. Wicket is a good choice. My favorite obviously as a core developer :). You might want to check out Tapestry and JSF too. Of these JSF is the closest to ASP.NET, and Wicket will attract most to people that are code oriented and want to have their HTML templates really clean. > The first thing I need to do is set up my development environment. Is there > an installation guide for Wicket? From the FAQ I read that Java 1.5 SDK is > not supported; I suppose I can use any IDE I please as long as I can select > or install a Java 1.4.x SDK for development, right? WIcket supports Java 1.4 and up. Choose any IDE and any servlet container you want. A good place to start is with Wicket's quickstart, http://wicket.sourceforge.net/wicket-quickstart/index.html. That should you get you started, please let this list know when you run into trouble. > Are there any restrictions on the version of Tomcat I can use? Should I > install the latest stable version (Tomcat 5.5), or is there some reason I > need an older version? Nope. You have to have JDK 1.4 or up, but that's about it. > Other than Tomcat and the Java SDK, are there any other tools that must be > downloaded separately from the Wicket download? The only runtime dependency you need is commons-logging (1.0.4). For compiling you need servlet-api 2.3 or up. They'll come with the quickstart project. Good luck, Eelco
