----- Original Message ----- Da : "Matej Knopp" <[EMAIL PROTECTED]> A : users@wicket.apache.org Oggetto : Re: "This time last year" .... is Wicket really a disappointment? Data : Thu, 24 Jul 2008 15:45:49 +0200
> Too many constrains? Really? > Just write a model that pull the image from whatever you > want (even as static object property for that matter). > Just because the model is serializable doesn't mean that > the model object has to be serializable. That's a big > differece. It's what I've done for v1. But it's what I don't like: for every model object I have to write a separate class. Now, I've been used to write adapter classes such as in this case for years, and usually I didn't complain very much. In EJB and JSF after all you have lots of code and complexity. Turning to Spring (but also EJB3) in the latest years I've been able to get rid of a lot of code in the business layer. My disappointment with Wicket is that I believed that it would have enabled me to do the same in the presentation layer. -- Fabrizio Giudici, Ph.D. - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [EMAIL PROTECTED] - mobile: +39 348.150.6941 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
