img
JAR File
Description
oxm
This modules provide support for OXM (object to XML mapping). Classes for
abstraction of XML marshaling and unmarshaling and support for popular tools like
Castor, JAXB, XMLBeans, XStream, and so on, are packed into this module.
web.struts
This module include all classes for integration between Spring and the Struts web
framework.
test
As we mentioned earlier, Spring provides a set of mock classes to aid in testing your
applications. Many of these mock classes are used within the Spring test suite, so
they are well-tested and make testing your applications much simpler. Certainly we
have found great use for the mock HttpServletRequest and HttpServletResponse
classes in unit tests for our web applications. On the other hand, Spring provides a
tight integration with the JUnit unit testing framework, and many classes that
support the development of JUnit test cases are provided in this module; for
example, the SpringJUnit4ClassRunner provides a simple way to bootstrap the
Spring ApplicationContext in a unit test environment.
transaction
This module provides all classes for supporting Spring's transaction infrastructure.
You will find classes from the transaction abstraction layer to support of the Java
Transaction API (JTA) and integration with application servers from major vendors.
web
This module contains the core classes for using Spring in your web applications,
including classes for loading an ApplicationContext feature automatically, file
upload support classes, and a bunch of useful classes for performing repetitive tasks
such as parsing int values from the query string.
web.servlet
This module contains all the classes for Spring's own MVC framework. If you are
using a separate MVC framework for your application, then you won't need any of
the classes from this JAR file. Spring MVC is covered in more detail in Chapters 17
and 18.
web.portlet
This module provides support for using Spring MVC in developing portlets for
deployment to a portal server environment.
Choosing Modules for Your Application
Without an IDE such as Eclipse or a dependency management tool like Maven or Ivy, choosing which
modules to use in your application may be a bit tricky. For example, if you require Spring's bean factory
and DI support only, you still need several modules including spring-core, spring-beans, spring-context,
spring-aop, and spring-asm. If you need Spring's web application support, you then need to further add
spring-web. For integration with Struts, you'll need spring-struts, and so on.
However, when using an IDE, especially SpringSource Tool Suite (STS), which will be used as the
default IDE for all examples in this topic, managing/visualize those dependencies becomes much
easier. In STS, you have the option to create a Spring template project and choose from a number of
project templates that suit your application. A Spring template project uses Maven for dependency
management, and STS also is bundled with m2e, an Eclipse plug-in project for Maven integration.
When you select the project template, Spring will create the project with the appropriate dependencies
declared for you. Thanks to Maven's transitive dependencies support, all required third-party libraries
will also be included automatically.
Search WWH :
Custom Search
Previous Page
Spring Framework 3 Topic Index
Next Page
Spring Framework 3 Bookmarks
Home