An especially powerful tag, the module tag is used to
describe a component binding for invocation and is best used in conjunction
with several nested <jinn:component/> tags. The
output of the module will be inserted in the place of the tag unless the
noRender attribute has ben set to
true. A full discussion of creating modules and
how they work is left to the section which describes modules. Here I will just
describe the tags and how they relate to the information in the section about
modules.
Setting the name allows for future reference to the
created module via the <jinn:render/> tag. If you do
not provide a name then a unique name will be generated when the object is
created.
By setting this to true you
prevent output from occurring at the location of the <jinn:module/> tag. This allows output to be delegated until an appropriate
<jinn:render/> tag or {jinn:render} embed is found.
The following example shows how to use the <jinn:module/> tag. See the section about <jinn:component/> tags for details about nested tags..
<jinn:module name="displayNews">
<jinn:component type="data"
name="loader"
source="//InterJinnWebsite/modules/news/mysqlLoader.php"
/>
<jinn:component type="logic"
name="manager"
source="//InterJinnWebsite/modules/news/manager.php"
/>
<jinn:component type="render"
name="render"
source="//InterJinnWebsite/modules/news/dhtmlPopup.php"
/>
</jinn:module>