> I've been thinking about the way in which wicket is an MVC framework and > whether people use it according to the MVC pattern.
The MVC pattern is bastardized - especially when it comes to web application frameworks - up to the point that it is hardly useful to use the term. Everyone seems to have their own interpretation. If you had to explain Wicket in MVC terms, my take would be that components represent the Controller and View (together, just like Swing), and the model is separated behind the IModel interface. But I think it is better to just let the whole MVC mania behind us and explain frameworks on their own terms :-) Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
