Page History

...

A better alternative is the @SubModule annotationImportModule annotation (@SubModule if using a Tapestry version lower than 5.4).

The value for this annotation is a list of additional classes to be treated as module classes, exactly as if they were identified in the manifest. Despite the name, there is no hierarchy of modules in Tapestry IoC.

Example:

@SubModule@ImportModule(
{ InternalTransformModule.class })
public final class InternalModule
{
  . . .

In general, your should only need to identify a single module in the JAR manifest, and make use of @SubModule to pull in any additional module classes.