I have some Java application development experience, but my web development experience is very small (mainly just a few simple servlets).  At my new job I am tasked with translating an architecturally simple ASP.NET application to J2EE (the company wants to standardize on Java).  I’m working alone, and have a lot of freedom in the tools and frameworks I choose. 

 

To make my job as easy as possible, I’m trying to make a wise trade-off between the time spent learning a new framework (I have no experience in any of them) versus the time spent coding.   I’m especially eager to minimize the time I spend wading through HTML code, as my experience there is also thin. 

 

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?

 

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?

 

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?

 

Other than Tomcat and the Java SDK, are there any other tools that must be downloaded separately from the Wicket download?

 

 

Reply via email to