J2EE is not "tied" with design patterns. Applying known design patterns just happens to be a best practice in the field of software engineering. Sun has made noise about using design patterns with Java/J2EE for a long time while the Microsoft camp was relatively silent. Nevertheless, the Microsoft camp has been (hopefully) using design patterns as well.
Originally posted by Leonildo Campos: Why is J2EE so tied with design patterns?
I don't aggree that J2EE is tied with Design Patterns... but I do concede that Design Patterns are considered very important by many in the J2EE community (and in other communties as well). I think part of the reason for this is the scope and complexity of J2EE. There are many ways to accomplish the same task and more than enough rope to hang yourself with. For this reason, people in the J2EE community have come together and defined a set of best practices in terms of Design Patterns. It always scares me to meet a "J2EE Architect" that doesn't have any knowledge the Design Patterns (in particular GoF and Core J2EE Patterns), he is doomed to make the same mistakes as those before him. J2EE is a tricky river to navigate; Design Patterns serve as our guide.
Hi, Design patterns are the effective way of attacking problems. Design patterns evolved by the experience of the architects. Re-inventing the wheel is NOT the game redesigning is....Thus patterns provide an efficient way to solve a problem. Cheers, Gaya3
I think the MVC2 (or "Model 2") architecture was designed especially for J2EE applications so in that way it won't fit into non-internet applications. You could ofcourse use the architecture by "porting" the concepts into a Swing application, for example, but I don't know whether it would work in that environment.
Originally posted by Lasse Koskela: I think the MVC2 (or "Model 2") architecture was designed especially for J2EE applications so in that way it won't fit into non-internet applications. You could ofcourse use the architecture by "porting" the concepts into a Swing application, for example, but I don't know whether it would work in that environment.
Actually, MVC has been around since the 70s and Smalltalk. It is very applicable to rich clients, actually it orignated in rich clients. MVC2 (terrible name), as Lasse pointed out, was previously referred to as Model 2 by Sun. It is basically a MVC architecture which uses a Servlet as the Controller, Java classes or EJBs as the Model, and JSP or some other templating engine as the View. Struts and WebWork are two widely available examples of MVC2. For more information on general MVC concerns (and other architectural patterns), I suggest: Patterns of Enterprise Application Architecture. For more information on MVC in the context of J2EE, I suggest this week's promo book: Core J2EE Patterns: Best Practices and Design Strategies.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop