Configure the web.xml file:
1. You only need to configure an ACTIONServlet regardless of how much subscriber included in your application. Configuring a plurality of ActionServlet classes to handle different features in applications, it is not necessary because servlet itself supports multithreading. Moreover, the current Struts framework is only allowed to configure an ActionServlet in the application.
2. Configure Welcome File List, see here, why do you want multiple welcome pages? How do this multiple pages call? It turned out to be like this:
Elements can contain multiple
Child elements, call from the narrator's first specified file, if this file exists, will return this file to the customer; if the file does not exist, look for the next welcome page file until it is found; if all The file does not exist, the server will return the error information of "HTTP 404 Not Found" to the client.
3.
The servlet mapping cannot be configured in the element, so it is not possible to directly use the Struts's action as a welcome file. However, it can be implemented by configuring a global forwarding item.
Configure multiple application modules:
1. Create a separate Struts profile for each sub-app;
2. Add each sub-application information in the configuration code of the web.xml ActionServlet;
3. Adopt
Elements or SwitchChaction classes to achieve switching between sub-applications.
Switch between multiple sub-application modules:
For example, switch from the default module to moduleb:
Http: // localhost: 8080 / tomodule.do? prefix = / moduleb & page = / index.do
Switch from Moduleb to the default module:
HTTP: // localhost: 8080 / Tomodule.do? prefix = & page = / index.do
I haven't done such an application in the current location, but I saw it on the book that it should be possible to improve the development efficiency.
And better management projects can be developed in parallel, but I don't know how to solve if some intersections.
