【正文】 Figure 194If you intend to perform many iterations of the same SQL statement against a database, you should consider batching with a PreparedStatement object. We39。ll see a differentiation in the timings of about 50%. Given a situation in which you need to make several tight calls to the database using a Statement, a predefined SELECT statement can save you a significant amount of time.Table 197: Select timings (in milliseconds)DriverStatementdefineColumnType( )OCI1310Thin1310Now that we39。s monly believed that calling stored procedures is faster than using SQL, but that39。s take a look at some numbers from Windows 2000. Table 199 lists all the statistics we39。 //Put hibernate cleanup code here (Exiting ())。 } public String getConfigFile() { return name。 // Identify the path ponent we will // use to select a mapping String path = processPath(request, response)。 for path 39。 // Set the content type and nocaching headers // if requested processContent(request, response)。 if (mapping == null) { return。 if (!processValidate(request, response, form, mapping)) { return。 if (action == null) { return。 you have to read the request as an InputStream and parse it to get the values. processPath(): In this method, Struts will read request URI to determine the path element that should be used for getting the ActionMapping element. processLocale(): In this method, Struts will get the Locale for the current request and, if configured, it save it inHttpSession as the value of the attribute. HttpSession would be created as a side effect of this method. If you don39。 // Process the returned ActionForward instance processForwardConfig(request, response, forward)。 } if (!processInclude(request, response, mapping)) { return。 } // Process any ActionForm bean related to this request ActionForm form = processActionForm(request, response, mapping)。 // General purpose preprocessing hook if (!processPreprocess(request, response)) { return。)。 } if (()) { (Processing a 39。 }}The class implementing PlugIn interface must implement two methods: init() and destroy(). init() is called when the application starts up, and destroy() is called at shutdown. Struts allows you to pass init parameters to your PlugIn class. For passing parameters, you have to create JavaBeantype setter methods in your PlugIn class for every parameter. In our HibernatePlugIn class, I wanted to pass the name of the configFile instead of hardcoding it in the application.Inform Struts about the new PlugIn by adding these lines to : strutsconfig ! Message Resources messageresources parameter= / plugin className= setproperty property=configFile value=// /plugin/strutsconfigThe className attribute is the fully qualified name of the class implementing the PlugIn interface. Add a setproperty element for every initialization parameter which you want to pass to your PlugIn class. In our example, I wanted to pass the name of the config file, so I added the setproperty element with the value of config file path. Both the Tiles and Validator frameworks use PlugIns for initialization by reading configuration files. Two more things which you can do in your PlugIn class are: If your application depends on some configuration files, then you can check their availability in the PlugIn class and throw a ServletException if the configuration file is not available. This will result in ActionServlet being unavailable. The PlugIn interface39。 (Value of init parameter + getConfigFile())。s JDBC development team to perform better than its OCI counterpart.原文二：Extending StrutsIntroductionI have seen lot of projects where the developers implemented a proprietary MVC framework, not because they wanted to do something fundamentally different from Struts, but because they were not aware of how to extend Struts. You can get total control by developing your own MVC framework, but it also means you have to mit a lot of resources to it, something that may not be possible in projects with tight schedules.Struts is not only a very powerful framework, but also very extensible. You can extend Struts in three ways.PlugIn: Create your own PlugIn class if you want to execute some business logic at application startup or shutdown. RequestProcessor: Create your own RequestProcessor if you want to execute some business logic at a particular point during the requestprocessing phase. For example, you might extend RequestProcessor to check that the user is logged in and he has one of the roles to execute a particular action before executing every request. ActionServlet: You can extend the ActionServlet class if you want to execute your business logic at either application startup or shutdown, or during request processing. But you should use it only in cases where neither PlugIn nor RequestProcessor is able to fulfill your requirement. In this article, we will use a sample Struts application to demonstrate how to extend Struts using each of these three approaches. Downloadable sample code for each is available below in the Resources section at the end of this article. Two of the most successful examples of Struts extensions are the Struts Validation framework and the Tiles framework. I assume that you are already familiar with the Struts framework and know how to create simple applications using it. Please see the Resources section if you want to know more about Struts. PlugInAccording to the Struts documentation A plugin is a configuration wrapper for a modulespecific resource or service that needs to be notified about application startup and shutdown events. What this means i