Apache Struts 2 Documentation > Home > Guides > Core Developers Guide > Zero Configuration |

Apache Struts 2 Documentation
Zero Configuration
Edit Page Browse Space Add Page Add News
Added by Ted Husted, last edited by Musachy Barroso on Feb 13, 2007 (view change) show comment hide comment
Comment: fix layout a little bit
View page history

| This feature is experimental. Feedback appreciated!

A "Zero Configuration" Struts application or plugin uses no additional XML or properties files. Metadata is expressed through convention and annotation.

As this is a new feature, and still being field-tested, the documentation is sketchy. But, here's what we have so far:

### Finding Actions

Set the "actionPackages" filter init param to a comma-separated list of packages containing Action classes in web.xml. The packages and their subpackages will be scanned. All classes in the designated packages that implement Action or end in "Action" are examined. The latter is to allow for POJO Actions that don't implement the Action interface.

Annotation Initialization actionPackages Filter Parameter in web.xml

    <filter>
      <filter-name>struts2</filter-name>
      <filter-class>org.apache.struts2.dispatcher.FilterDispatcher</filter-class>
      <init-param>
        <param-name>actionPackages</param-name>
        <param-value>com.foo.bar,com.baz.quux</param-value>
      </init-param>
    </filter>

We should probably add an action annotation, so that POJOs can itall with annotations.

### Examples

The only example right now is in the showcase, where the person package uses the classpath scanning configuration.

### Action and Package name

The subpackage name makes the namespace, and the action class name makes the action name. If there is an "Action" suffix, it is dropped before creating the action name. Therefore, if the configured package is com.myapp.actions and the Action is com.myapp.actions.member.EditAction, you can access it via http://server/myapp/member/edit.action.

### Results

Results are defined with the Result and Results annotations at the class level.

### Namespaces

The Namespace Annotation overrides the namespace.

### Parent Package

The ParentPackage Annotation has the XWork package (an XWork package is created per Java package) to extend the defined package. Multiple packages can be specified through annotations on multiple Actions in the package.

### Feedback

Stay tuned to this page for additional details and documentation. If you have a chance to try the zero configuration feature, please share any experiences on dev@ and here.

### See also

- Zero Configuration Scanning Use Case
- RESTfulActionMapper

## Next: Annotations