Versions Compared

Old Version 4

changes.mady.by.user Philip Luppens

Saved on

compared with

New Version Current

changes.mady.by.user Jeff Black

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Tip

Dependency injection removes the responsibility for object creation and object linking from the objects themselves to a factory. The factory is often provided by an Inversion of Control (IoC) container. For an overview of Inversion of Control containers and the Dependency Injection pattern, please see Martin Fowler's article.

Internally, the framework uses its own dependency injection container that is very similar to Google Guice. Both were originally developed by Bob Lee. Plugins are available to integrate applications with other IoC containers (e.g. Spring Plugin, Plexus Plugin). An application can even use a local copy of Google Guice for dependency injection needs.

(info) Actions can still be instantiated via Spring configuration by way of the Spring Plugin, but Spring is entirely optional.

(warning) The WebWork/XWork IoC container utilized by WebWork 2.1 is not supported by Struts 2.

Next: Profiling

Note

These documents are out of date. As of WebWork 2.2, the WebWork IoC container has been deprecated (though not removed) and the WebWork team recommends you use Spring for all your IoC needs

Inversion of control is a way to handle dependencies of objects. In WebWork, objects that are have their dependencies managed are called "components". For an overview of of Inversion of Control (also referred to now as Dependency Injection), please read Martin Fowler's article on IoC at http://www.martinfowler.com/articles/injection.htmlImage Removed. Besides WebWork's IoC container, there are numerous other containers available for you to use, including Spring and Pico.

...