Matthew Phillips
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
You can build an MVC architecture using J2EE without Struts. You would need to build a servlet/JSP combination for every possible invokation. And every servlet would need some control logic in front to process the request and then ot would need to determine which JSP to invoke and what parameters to pass to that JSP. You would want it to be flexible so it would make sense to keep the controlling parameters in the web.config or other parameter file. Of course, our servlets are starting to get repetitive with all that control logic so it might make sense to write one control servlet that does all the grunt work and then passes control to other servlets to do the business logic. But now these servlets all need to do lookups from our config files to figure out which JSP to invoke so maybe that should be aprt of the controlling servlet too. So maybe the controlling servlet shouldn't pass control but should invoke an Action object that does some stuff and then when it is finished gives control back to the controller to invoke the JSP. Whoops... I just wrote Struts!Originally posted by Ken Robinson:
So far, most good things I have seen about STRUTS are easily done without STRUTS.
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
Originally posted by Thomas Paul:
You can build an MVC architecture using J2EE without Struts. You would need to build a servlet/JSP combination for every possible invokation. And every servlet would need some control logic in front to process the request and then ot would need to determine which JSP to invoke and what parameters to pass to that JSP. You would want it to be flexible so it would make sense to keep the controlling parameters in the web.config or other parameter file. Of course, our servlets are starting to get repetitive with all that control logic so it might make sense to write one control servlet that does all the grunt work and then passes control to other servlets to do the business logic. But now these servlets all need to do lookups from our config files to figure out which JSP to invoke so maybe that should be aprt of the controlling servlet too. So maybe the controlling servlet shouldn't pass control but should invoke an Action object that does some stuff and then when it is finished gives control back to the controller to invoke the JSP. Whoops... I just wrote Struts!
Poorav Chaudhari
CNSS/NSA Infosec Professional,<br />Software Engineer
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
What you're getting from Struts is a pre-debugged, disciplined framework.
CNSS/NSA Infosec Professional,<br />Software Engineer
Sorry, I can't can't take anyone seriously who's worried about speed but using Java, the Internet, databases, etc. You think STRUTS has overhead???!!!
The advantage is that resources are cheap, but programmers (even outsourced ones!) are expensive. You can't save nanoseconds to spend later, but dollars (rupees, ringitt, whatever) are another matter.
What you're getting from Struts is a pre-debugged, disciplined framework.
No silver bullet. One size DOESN'T fit all. You pays your money and you takes your choice. Sometimes you choose wrong and have to do it over. Which is why Fred ("The Mythical Man-Month") Brooks offered his excellent advice: "Plan one to throw away". Emphasis on the word "Plan".
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |