Ftp Web Hosting - PHP, MySQL, Java, Jsp, Servlet, Tomcat, Ssh Blog

C.4 Tiles Site The creator of the Tiles library, Cedric Dumoulin, also maintains his own site at http://www.lifl.fr/~dumoulin/tiles/. You can find tutorials and general information on Tiles at this site, and you can also download the latest version of the library. C.5 Nested Tags Site The Nested tag libraries were released in November 2001 and added to the core Struts framework several months later. The creator of the libraries, Arron Bates, maintains a site where you can find great tutorials and tons of information on the nested tags. The URL for his site is http://www.keyboardmonkey.com/next/index.jsp. C.6 The Struts Console There are several Struts GUI tools available and more are created every day, but one of the best and most widely used is the Struts Console. The Console application was briefly discussed in Chapter 4 and is available for download at http://www.jamesholmes.com/struts/. The creator of the Console, James Holmes, recently became a committer to the Struts framework. C.7 Easy Struts Project The Easy Struts Project, hosted on SourceForge, provides tools and plug-ins for various IDEs in order to increase productivity when building Struts applications. There are plug-ins for JBuilder, Eclipse, and other popular IDEs. You can find more information on the Easy Struts Project at http://easystruts.sourceforge.net.
Searching for affordable and proven webhost to host and run your servlet applications? Go to Linux Web Hosting services and you will find it.

B.5 Tips on Installing Struts in JRun The latest version of JRun should require no extra steps. Appendix C. Resources This appendix provides a list of resources that you can use to further your knowledge of Struts. C.1 The Struts Mailing Lists By far the two best places to learn and ask questions about the Struts framework are the two mailing lists, STRUTS-USER and STRUTS-DEV. The user list currently has around 1,750 subscribers and has been growing at a rate of 50 to 100 new users a month for the past year or so. The STRUTS-USER list is designed for Struts developers, both new and experienced alike. You definitely should consult the FAQ (http://www.tuxedo.org/~esr/faqs/smart-questions.html) before posting any questions. There’s not much flaming on the list, but you will get pummeled if you don’t think about the question you’re asking before posting it. The STRUTS-DEV mailing list is devoted to those working on the framework itself. Anyone can post on it, but you should not ask questions here about your application, or questions that can be better answered on the user list. In almost all cases, unless you are contributing to the development of the framework or bug fixes, or would like to get involved in this manner, you should be posting to the user list. You can subscribe to either or both lists from http://jakarta.apache.org/struts/index.html#Involved. There are also several ways to search the lists (you can search through many Jakarta mailing lists, not just the ones for Struts). One option for searching the Struts mailing lists is to go to http://www.mailarchive. com/lists.html and select whether you want to search through the DEV or the USER list. Another way to search is to use the eyebrowse feature from the Apache Software Foundation (http://nagoya.apache.org/eyebrowse/). You can search through all of the Apache mailing lists here as well. Yet another method is to use the excellent search capabilities of the jApache site at http://www.japache.org/index.jsp. C.2 The Struts Resource Web Page There are many interesting and informative links on the main Struts site. One of the best is the Struts Resource Page (http://jakarta.apache.org/struts/resources/index.html). The list is divided by category (tutorials, articles, books, etc.). You could easily spend a solid month following all of these links. C.3 Validator Site The creator of the Validator, David Winterfeldt, still maintains his own site at http://home.earthlink.net/~dwinterfeldt/. You can find tutorials, advanced user guides, and general information on the Validator framework, and you can also download the latest version of the framework.
We highly recommend you visit web and email hosting services if you need stable and cheap web hosting platform for your web applications.

2. Copy all of the .tld files to the web application’s WEB-INF directory. 3. If you plan to use the Validator framework, copy the validation-rules.xml file to the WEB-INF directory. See Chapter 11 for more information on the configuration files required by the Struts Validator. 4. Create a web application deployment descriptor (web.xml) and copy it to the WEB-INF directory. See Chapter 4 for details on how to configure the web.xml file. 5. Create a struts-config.xml file and copy it to the WEB-INF directory. See Chapter 4 for details on how to configure the configuration file for Struts. 6. Create a properties file called commons-logging.properties and copy it to the WEB INF/classes directory. Put the following line in the file: org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog 7. Create a Struts resource bundle and copy it to the WEB-INF/classes directory. See Chapter 12 for how to format this bundle and Chapter 4 for how to configure the Struts configuration file to use this bundle. That’s really all there is to installing the Struts framework. You still have to build the necessary JSP pages and other framework components, such as Actionand ActionForm classes, but this is what is required to get the environment running. It’s highly recommended that you play around with the example applications that are distributed with Struts. They are complete web applications, packaged as WAR files that you can copy to the container’s webapps directory. You have the option of using one of many different containers to run the Struts framework. In many cases, the steps just described should be followed exactly. However, not all containers are created equal, and some require modifications to the steps listed. The necessary modifications, if any, are described below. B.2 Tips on Installing Struts in Tomcat Depending on which version of Tomcat you use, you may have to perform a few additional steps. Because Struts 1.1 requires a container to support the 2.2 Servlet specification and the 1.1 JavaServer Pages specification, the minimum version of Tomcat that will work is Tomcat 3.2. However, if possible, you should attempt to use the latest version of Tomcat (4.X), as it has many improvements that allow the Struts applications to perform better. B.3 Tips on Installing Struts in WebLogic With earlier versions of WebLogic such as 5.1, you had to perform several non-intuitive steps in order to get Struts to work correctly. Some of these problems had to do with WebLogic unpacking only *.class files and not other files like JARs. However, with WebLogic 6.0, 6.1, and now 7.0, there shouldn’t be any extra steps to perform. B.4 Tips on Installing Struts in WebSphere If you have the latest patches applied, no extra steps should be required. However, developers have reported major headaches with installing Struts on Version 3.5.
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.

If the build is unsuccessful, you will get a failed message, usually with enough information to determine the cause. For example, if you forget to put the xalan.jar in the /lib directory, the output will look similar to that in Figure B-2. Figure B-2. A stack trace is usually included in failed builds Assuming that the build was successful, the Struts binaries and dependent files are copied to the dist directory underneath the top-level source distribution directory. B.1.2 Installing the Binary Distribution Download the binary distribution and unpack it into a directory. The files are in a subdirectory called jakarta-struts within the distribution. As with the source distribution, you can download either a ZIP file or a compressed TAR file. You can obtain the binary distribution from http://jakarta.apache.org/site/binindex.html. If you built Struts from the source distribution, the binary files will already be unpacked into the dist/lib directory of the top-level source distribution directory. The following steps need to be performed for a Struts application to work properly. Any necessary container-dependent modifications to these steps are discussed in the sections for the individual containers later in this appendix. 1. Copy all of the JAR files from the distribution’s lib directory to the web application’s WEBINF/lib directory.
In case you need affordable webhost to host your website, our recommendation is ecommerce web host services.

The next step is to create a build.properties file that specifies environmental dependencies such as the location of the third-party JARs extracted in the previous step. The Struts source distribution provides a build.properties.sample file in the top-level source distribution directory. Open this file and rename it build.properties. You need to customize this file for your particular environment. The file paths are relative to the location of the properties file. For example, to reference the CommonsBeanUtils JAR file that is located in a directory called lib one level up, you would need to change the properties file to look like this: # The JAR file containing version 1.0 (or later) of theBeanutils package# from the Jakarta Commons project. commons-beanutils.jar=../lib/commons-beanutils-1.3/commonsbeanutils.jar Once you have all of the file paths set in the build.properties file, you are ready to turn the Struts source files into Struts binary files. Make sure Ant is installed and configured correctly, and make sure you downloaded the xalan.jar file and placed it in the /lib directory (this is needed so that an Ant task can process the XML documentation files). You will need to be able to execute Ant from the command line in the top-level source directory. Once you’ve completed these steps, go to the directory where the build.properties file is located and type: ant dist Messages will be spewed out in the console. When they finally stop, they should show that the build was successful, as in Figure B-1. Figure B-1. A success message is printed when complete
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

Servlet API classes All servlet containers should contain the necessary files; just make sure the necessary JARs are in the classpath for the build tool. XML parser One that supports JAXP Version 1.0 or later. The Xerces parser is compatible and can be obtained from http://xml.apache.org/xerces-j/. Xalan XSLT Processor Version 1.2 or later. Note that some problems have been reported with Version 2.0. The processor is used to convert the XML documentation files into HTML documentation files. The processor also includes the Xerces parser. You can download Xalan from http://xml.apache.org/xalan-j/index.html. JDBC 2.0 Optional package classes The Struts framework supports an implementation of javax.sql.DataSourceand therefore requires the JDBC 2.0 Optional classes to be present. You can obtain the JDBC 2.0 classes from http://java.sun.com/products/jdbc/download.html. You will also need to download the third-party packages listed in Table B-1 and extract the JAR files included with the packages. Each package has both a source and binary distribution available. Unless you are a true masochist, you should download the binary distributions of these packages. Table B-1. Third-party packages required for Struts compilation Package name URL Commons BeanUtils http://jakarta.apache.org/commons/beanutils.html Commons Collections http://jakarta.apache.org/commons/collections.html Commons Digester http://jakarta.apache.org/commons/digester.html Commons Logging http://jakarta.apache.org/commons/logging.html Commons Pool http://jakarta.apache.org/commons/pool/index.html Commons Services http://jakarta.apache.org/builds/jakarta-commons/nightly/ Commons DBCP http://cvs.apache.org/viewcvs/jakarta-commons/dbcp/ Commons Validator http://cvs.apache.org/viewcvs/jakarta-commons/validator/ Jakarta ORO http://jakarta.apache.org/oro/ The URL http://jakarta.apache.org/commons/components.html provides a nice summary of the different release schedules of the Commons components. Extract the binary distributions of each of these packages and put the JAR files somewhere that you can easily reference them, as will need to in the next step. Each package is extracted into its own subdirectory. You can leave the JAR files there for easier reference.
Looking for affordable and reliable webhost to host and run your business application? Then look no more and go to servlet web hosting services.

Commons Logging Appendix B. Downloading and Installing Struts This appendix provides instructions and helpful tips on installing the Struts framework. All attempts have been made to ensure that these instructions work with the latest available versions of the containers. If you encounter any problems, check the STRUTS-USER mailing list. B.1 The Binary Versus Source Distributions There are two distribution methods for the Struts framework, source and binary. The source distribution gives you more control over the build package environment. However, this method is not for beginners. Unless you have a specific need (e.g., you need to insert a modified class file into the build), you should stick with the binary distribution. This section presents both methods. B.1.1 Building Struts from the Source Distribution You can obtain the source packages of Struts and the rest of the Jakarta projects from http://jakarta.apache.org/site/sourceindex.html. Several different versions are usually available, so be sure to get the one that’s appropriate for your needs. There is always a nightly build of Struts that includes the latest changes and fixes. In most situations, you’ll want to go with the nightly build, but be aware that it may also include new bugs. When choosing a download, you have the option of selecting a ZIP file or a compressed TAR file. Choose the one that is appropriate for your environment. Once you have downloaded the appropriate version, extract the contents into a directory. The directory doesn’t have to be empty, but it’s easier if it is. The Struts source distribution file unpacks everything into a subdirectory called jakarta-struts. Before you can build the source files, you will also need to download several prerequisite software packages (if they’re not already installed in your environment). The following list describes the required software: Java SDK Version 1.2 or later. You can download the latest version from http://java.sun.com/j2se/. Servlet container One that supports the 2.2 Servlet specification or later and the 1.1 JavaServer Pages specification or later. Ant build tool Version 1.3 or later. You can download the latest version from http://jakarta.apache.org/ant/.
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

A.5 The Struts Validator The Struts Validator is a validation framework that supports both Struts and non-Struts applications. It was designed with Struts in mind, though, and it has many nice features that are desirable for the types of applications typically built using Struts. Chapter 11 covers the Struts Validator in detail. A.5.1 Change to the ORO Package One thing is worth mentioning as far as upgrading goes. Earlier versions of the Validator framework relied on the RegExp package from Jakarta. This has been switched to Jakarta’s ORO package. See Chapter 11 for more details on why this change was made and how it affects the configuration of the Validator. A.6 Change to Commons Logging The entire Struts framework now relies on the Commons Logging library, which is an open source logging API from Jakarta. It provides a simple, consistent logging API that can be used within all applications and that allows different implementations to be plugged in dynamically. You will need the Commons Logging JARs, but these should already be included with the Struts framework. This change also required some configuration settings to be added. Chapter 15 covers the Commons Logging library as well as general logging in a Struts application. A.7 Removal of Admin Actions Several “administrative” actions were included with previous versions of the Struts framework. These actions could be used for such things as reloading a Struts application (including the configuration settings) without shutting down the application. The ability to add new action mappings dynamically was also supported. These actions have been removed from the framework and are no longer available. If your application requires this functionality, you will have to provide it programmatically. A.8 Deprecation of the GenericDataSource The org.apache.struts.util.GenericDataSourceclass has been deprecated. This class was never designed to be a full-scale data source implementation for large, high-availability applications. It was meant for smaller applications, and never had the advanced features found in the more mature data source products. If you need a data source implementation, it’s recommended that you use either one that is available with your container, or the one available in the Commons DBCP project at http://cvs.apache.org/viewcvs/jakarta-commons/dbcp/. A.9 Dependency on Commons Projects The Struts framework now has the following dependencies on packages from the Jakarta Commons project: Commons BeanUtils Commons Digester Commons Collections
Looking for affordable and reliable webhost to host and run your business application? Then look no more and go to servlet web hosting services.

Starting with 1.1, exception handling is now part of the core framework. You can declaratively configure which exceptions that actions can throw and what should happen when they occur. Chapter 10 covers exception handling. A.4.2 Dynamic ActionForms A new type of ActionForm class was added in 1.1, and broader support for it has been added throughout the entire framework. The DynaActionForm and its subclasses allow you to configure form-bean instances in the Struts configuration file. This has the effect of saving development time because you are no longer required to create ActionForm classes. It’s a little too general to say that you’ll never need to create another ActionForm class however, the number of them that you need to create should be drastically reduced. See Chapter 7 for more information on this new feature. A.4.3 Plug-ins The PlugIn feature was added to the Struts framework to provide a mechanism to notify and initialize services when the Struts application starts up and shuts down. There is a wide range of possibilities for this feature, and in fact, the Struts Validator and the Tiles library both take advantage the PlugIn mechanism. See Chapter 9 for more information on using plug-ins in your applications. A.4.4 Multiple Application Modules The addition of application modules to the framework allows a single Struts application to support more than one Struts configuration file. This facilitates a project being divided into subprojects, each with its own configuration file. While this might sound more complicated, it allows better support for parallel development. The support for multiple application modules is still undergoing some changes and modifications. At the time of this writing, you can use extension mapping only for the controller servlet, and it may be a while before the rest of the components have full support for this new feature. A.4.5 Nested Tags Nested tags are a set of JSP custom tags that were added to the Struts framework to give developers better control over accessing properties from a JavaBeans object graph. Many JavaBeans objects contain nested JavaBeans objects that can be referenced by the parent bean. For example, a Customer object may hold a reference to an Address object. To better support the nested nature of these JavaBeans in the Struts views, the nested tags were created. The tags within the Nested tag library are discussed in Chapter 7.
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check mysql web server services.

A.1 ActionServlet and RequestProcessor A new class called RequestProcessor was added to the framework in Struts 1.1. This class takes over much of the work that the ActionServlet class performed in previous versions. With 1.1, you can still configure the class name of the ActionServlet that you want to use for an application in the web.xml file, but the RequestProcessor now carries out much of the real request-processing work. By default, applications use the org.apache.struts.action.RequestProcessorclass to handle all incoming requests. You are not required to do anything if the default behavior suits your requirements. You can, however, choose to override the default implementation with one of your own. You can switch implementations by configuring the controllerelement in the Struts configuration file. See Chapter 4 for more details on configuring the controller element. A.2 Modifications to the Struts Action Class The Struts base Action class has been modified with a new method called execute( ). This new method should be called instead of the perform( )method. The main difference between the two is that the execute( )method declares that it throws java.lang.Exception, whereas the earlier perform( ) method declared IOExceptionand ServletException. This change was necessary to facilitate the new declarative exception- handling feature that was added to Struts 1.1. The perform( )method has been deprecated and should not be used. A.3 Changes to web.xml and struts-config.xml There have been many changes to the two configuration files required by Struts applications. The web.xml file has had several initialization parameters removed; they are now supported by elements within the struts-config.xml file. The web.xml file also supports a few new parameters. The elements of both files are covered in Chapter 4 and will not be repeated here. You can check the Struts DTD to see exactly which elements are supported in a Struts configuration file. You will need to update your Struts configuration file to use the latest DTD, which is called strutsconfig_1_1.dtd. You will get many parsing errors if you forget to do this. A.4 New Features of Struts 1.1 The new features in Version 1.1 of the Struts framework are covered in detail throughout this book. Descriptions of the most important ones are provided here. A.4.1 Declarative Exception Handling Prior to 1.1, exception handling was completely left up to the application. There was no support for it in the core framework, and developers were left to their own devices to figure out how to handle exceptions within an application.
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.