I am sure that in a week or two that might be apparent to me. However right now I am exposed to everything that ActionServlet and MultipartRequestWrapper hid from view. Using Struts in my programming, the controller part of the MVC was hidden.
For example, one of the first questions I had was: How in the world do I control where a successful action will forward to? Where do I set that?
My questions are pretty much in that ballpark.
:)
Basically, Denis, you can control what requests go to what Servlets in web.xml, which is why Struts usually captures requests that end in ".do". Struts is one way of using Servlets and does the job by running every request within its "domain", i.e. those ending with ".do" as a rule, through a controller Servlet, viz. ActionServlet.
Essentially, Struts is a one Servlet application, using the Servlet as the C in MVC.
You can use more Servlets if you want, but using Struts is to use Servlets in one particular way, albeit a very interesting and successful way. There is not much to learn about Servlets with Struts. Struts is just all about things non-Servlet in nature. Again, I would strongly suggest you spend this evening with a book like Jason Hunter's book on Servlets.
You can study and run a pure Servlet application and use Struts at the same time. Struts is not "not pure Servlets" anywhere. If someone is trying to tell you that somehow Struts and Servlet applications differ, they are mixed up. Whatever application structure you use in a web context, it will of necessity have to do a lot like Struts does if it is based on Servlets.
Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
