(with respect to my project of translating a simple ASP.NET application to J2EE)
Eelco: > Sure. Wicket is a good choice. ...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. My first thought was to use JSF, because the translation from ASP.NET would likely be more direct. What made me rethink this was the problem of translating ASP.NET capabilities not yet in the JSF reference edition (e.g. a date picker, or the ability to return a table as a MS Excel spreadsheet). That might require a more sophisticated knowledge of the way JSF works inside. My intuition tells me that with a conceptually simpler framework, solutions to such problems should be more obvious. Also, I feel more confident of my ability to eliminate redundancy through abstraction when working in code than in XML or HTML. Me: From the FAQ I read that Java 1.5 SDK is not supported > Wicket supports Java 1.4 and up. Choose any IDE and any servlet > container you want. So when the FAQ asks, "When will Wicket use Java 5?" -- they're asking about using Java 5 to develop the Wicket framework, not wicket applications? /Frank ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
