Script: moduleList-element

The purpose of modulelists is to introduce a shorthand form for homogen modules. The module lists are transformed to modules before the modulestructure is set up. The script may contain any number of modulelists. A module list must be contained in a module.

Note that modulelists introduce some limitations on remotecollections, see CollectRemote . It also takes over control of the sequence of modules. You should consider modulelists only in special cases where you want a large number of homogen modules for special purposes, like producing modules for a set of products, a calendar, a team of people.

<modulelist catalog="" 
              template=""  
              sourcesuffix=""  
              targetsuffixr="" 
              books=""/>

catalog(mandatory)	Any string that represents a catalog, absolute or relative to the scripts catalog. Contentfiles are supposed to be in this catalog, and prepared modules will be placed in this catalog.
template(optional)	Identification of a template by id. If template is ommitted, the source file is considered template (with no content-file)
sourcesuffix(optional)	Suffix of actual content-files. Default is xml
targetsuffix(optional)	Suffix of resulting modules. Default is html.
books(optional)	A commaseparted string of books that these modules should be a part of. Default value is _all.

Examples:

<modulelist template="P" 
            sourcesuffix="xml" 
            targetsuffix="html" 
            catalog="${lists}" 
            books="personer"/>