Create a MyEclipse Web Project (or Eclipse Dynamic Web Project) called MySpringProject.

Right-click on the MySpringProject project, and choose MyEclipse > Add Spring Code Generation Capabilities...

Figure 1. Add Spring Code Generation Capabilities Wizard

The first panel is for specifying whether the Spring Nature should be applied to the project. This option is disabled by default. For this tutorial we'll keep it disabled. Click the Next button.

Figure 2. Basic Setup

The Web Layer Generation panel is used for enabling and configuring code generation for the web layer of a Spring application. By default it is enabled, and you can specify the project and folders to generate to. For this tutorial we'll use the defaults.

Figure 3. Initialize web layer

The source, resources and content folders can be any folder in the "target project". If the folders don't exist, they will be created. In the case of the source and resources folders, they will also be configured as Eclipse source folders in the project. Since this project is a web project, the content folder is automatically set to the content folder that was specified in the New Web Project wizard. Click the Next button.

The next three panels are nearly identical to the Web Layer generation panel, however these panels are used to configure the other layers of a Spring web application. By default the other layers are also enabled, and the source and resource folders are the same as the web layer. For this tutorial we'll use the defaults. Click the Next button.

Figure 4. Initialize service, domain and DAO layers

The Runtime Dependencies panel is for adding Spring and dependent libraries to the current project. While you can add and remove libraries from the project by hand, this panel can bootstrap the project with a full set of libraries typically needed by a Spring application. In addition to deciding which libraries are added, you can also specify which version of Spring (2.5 or 3.0) that you want to use and how you want the libraries added to the current project. Spring 2.5 and the use of Eclipse classpath containers is the default. Click the Next button.

Figure 5. Initialize runtime dependencies

The Summary panel provides a summary of all the actions to be performed by the wizard when the Finish button is clicked. Click the Finish button.

Figure 6. Review summary

The first thing that you will notice is that multiple classpath containers have been added to the project. You now have all the libraries necessary for a Spring web application.

Figure 7. Classpath Containers

If you want to see the libraries that are represented by a specific classpath container, you can expand the container to see a list of libraries. For example, if you expand the Spring 2.5 Core Libraries container, you will see the list of libraries that correspond to Spring 2.5 Core.

Figure 8. Container Libraries - Spring 2.5 Code Libraries

While it's beyond the scope of this tutorial, with MyEclipse for Spring you can also customize the libraries that are in each of these classpath containers.

Per the default configuration of the wizard, the generated folder was created and setup as an Eclipse source folder. This is the folder where generated Java source code will be generated.

Figure 9. Generated Folder

The resources folder was also created and setup as an Eclipse source folder. This is where all application configuration files are generated to.

Figure 10. Resource folder

You will notice that various files were generated into the resources folder. Here's a summary of the generated files.

To web content folder was modified to support Spring web applications. In particular the applicationContext.xml file was added, and the web.xml was updated.

Figure 11. Bootstrapped Web Content

The Spring DSL View was added to the project, and it can be seen using the Project Explorer. The Spring DSL shows a hierarchical view of the project's Spring DSL artifacts, and it can be used for configuring the Spring DSL and managing any Spring DSL artifacts.

Figure 12. Spring DSL View