On Sat, Aug 13, 2005 at 07:48:15AM -0400, Danny Rubis wrote: > Hey! > > I have been with servlets since day one. You may recognize me for I > responded > many times years ago when servlets were been formulated and thereafter > answering > questions as a mentor on this list. For the most part, servlets have > evolved into some > thing good. I don't like the "higher up the stack" based on servlets, > i.e. STRUTS and > I probably won't like JSF. I have written a 'better' STRUTS. It is > much faster and > much easier to add capabilities. My apologies go McClaughlin, et al. > For one, I just > don't think XML is a good way to communicate with the Controller in the > MVC model. > > If I have some time, maybe when I retire, I will write something on how > to write a good > Controller. Most projects 'out here' don't need the enormous overhead > of STRUTS to > do an MVC. How many files do you have to create? Five??? I really > don't know > because I just don't use and don't need STRUTS. BTW guys, don't put MVC > experience > on your resumes just because you know how to use STRUTS. I see that on so > many resumes. Only the writers of STRUTS can claim MVC. R > Jason, that being said, I don't care which Approach you take. Just > write something so we can > have some fun and you can make another "million dollars" (quote by Dr. > Evil). :>) I'll buy > your book. > > Sans adieu, > Danny Rubis
I usually just lurk in the shadows on this list, but mr. Rubis' rather ill-begotten views on projects such as Struts made my fingers itch. I have not been on this list since day one. I have however, had a good amount of experience with servlets (both http and sip). I do not claim servlet-mastery, but I do have a good understanding of how they function and when to use a raw servlet, and when to avoid that. The Struts project was one of the first (in my eyes) real efforts to bring the MVC paradigm to servlets. Web applications will always have the inherent problem of not being able to isntantly display changes in the model to the user due to the way in which the HTTP protocol works. GUI programs have a lot easier time doing this. After Struts had a strong footing, a load of new projects mushroomed allowing the MVC in HTTP to go further and further. Whether data passed to the MVC controller is XML, binary or whatever is not important to the paradigm. It is the paradigm as such that is an important mechanism for the separation of concerns, how it is implemented is not even relevant. I have used a Struts a lot and have found it not only to be very simple in use, but also a close adherent to the MVC paradigm (take input, process, select a view to display). It also speeds up development time a lot, since all configuration (like form behaviour) can happen in just a few files. What is "MVC experience"? Coming up with the idea for the first time? Building an MVC framework that implements the paradigm? Using that framework? Using software that uses the framework? Where do we draw the line? It's like saying a In my opinion having knowledge of the subject and knowing how it works is enough to state one has "MVC experience". What you are stating is like saying that a car mechanic cannot have experience with car repair because he didn't come up with the original design of the car. cheers, Ben -- Ben Turner SIEMENS - COM D MN B tel: +32 14 252326 ~ Scientia Vincere Tenebras ~ ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
