I don't think ASP.NET is superior to Wicket in any of the items you described, honestly.
ASP.NET requires more work for "including" separate pages, "panels", etc. I found the Panel much more elegant in Wicket than a "User Control" in ASP.NET. I think you're right, however, the one-off stuff that you don't plan to grow or maintain regularly is well suited for ASP.NET....smaller applications that don't require much thought. If you're in a Windows-only environment and it's already there for you...it's just convenient. I still think it can be done more productively in Wicket. And, I never want to have to write a pile of ADO.NET code for a more-than-trivial web app again...I've been spoiled by Hibernate & EJB3. On 5/5/06, Frank Silbermann <[EMAIL PROTECTED]> wrote:
For the last couple of months I've been building in Wicket to replace an ASP.NET application. My impression is that ASP.NET is the best thing I've ever seen for doing a "one-of". Any page content that I'm going to build and use in just one page (or simply "include" with no modifications in a variety of places) is incredibly easy to do in ASP.NET. Wicket is far superior for situations where I need to do the same _kind_ of thing in a variety of different places, but with variations. With Wicket it is easier to build and use a component with a variety of constructors, and with methods that can be easily replaced each time I use it. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vincent Jenks Sent: Thursday, May 04, 2006 5:49 PM To: [email protected] Subject: Re: [Wicket-user] The other side of Wicket ... Oh yeah, just jokes, .NET is a pretty great technology...though it still requires far more work than the EJB3+Wicket combo. MS's tools are great, they have a snazzy IDE...but I still prefer Eclipse...perhaps because of its open nature and breadth of industry support both pro & amateur. The tools are also the problem....you can't rely on much else outside of MS's visual studio tools to do the job. I personally hate WYSIWYG environments and writing asp.net pages, controls, etc. w/o the editor can be quite tedious. JSF's similarity to ASP.NET is one reason I didn't want to use it...not to mention all of the strange issues I had heard of w/ JSF 1.1. .NET has it's place...but now that EJB3 is a finalized spec...I doubt it can keep up w/ Java EE 5 and beyond in a one-on-one comparison. stinfo/wicket-user ------------------------------------------------------- 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?cmdlnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
------------------------------------------------------- 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&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
