Nick's comment on here about a week ago got me to at least look at Wicket. http://wicket.sourceforge.net/ Has anyone actually used it for a real-world application? I'd be curious on your thoughts.
So far, with my limited two days of looking over the examples and example code, I'm not so sure of it's place in the framework world. My biggest contention is with the claim on the page http://wicket.sourceforge.net/Introduction.html "Wicket is all about simplicity. There are no configuration files to learn in Wicket. Wicket is a simple class library with a consistent approach to component structure. In Wicket, your web applications will more closely resemble a Swing application than a JSP application. If you know Java (and especially if you know Swing), you already know a lot about Wicket." What's so much easier about understanding how their Java classes work as an API vs understanding how XML configuration files work? All they did was move any xml complexity into understanding how the overall framework API works (and to compound the matter, there really is very little documentation). I'm just not so sure what it buys me over using a component based framework such as JSF. The biggest strength I see in the framework is in regard to page markup: "Wicket, more than any other framework gives you a separation of concerns. Web designers can work on the HTML with very little knowledge of the application code (they cannot remove the component name tags and they cannot arbitrarily change the nesting of components, but anything else goes). Likewise, coders can work on the Java components that attach to the HTML without concerning themselves with what a given page looks like. By not stepping on each other's toes, everyone can get more work done." Since I'm the one always having to handle the html in my JSPs anyway, the above isn't that big of a deal to me. -- Rick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
