| This filter goes through the generated page response prior and
places requested resources at the appropriate inclusion markers.
This is done to let dynamic content (e.g. plugins, editors)
include custom resources, even after the HTML head section is
in fact built. This filter is typically the last filter to execute,
and it must run after servlet or JSP code that performs
redirections or sends error codes (such as access control methods).
Inclusion markers are placed by the IncludeResourcesTag; the
defult content templates (see .../templates/default/commonheader.jsp)
are configured to do this. As an example, a JavaScript resource marker
is added like this:
<wiki:IncludeResources type="script"/>
Any code that requires special resources must register a resource
request with the TemplateManager. For example:
<wiki:RequestResource type="script" path="scripts/custom.js" />
or programmatically,
TemplateManager.addResourceRequest( context, TemplateManager.RESOURCE_SCRIPT, "scripts/customresource.js" );
See Also: TemplateManager See Also: com.ecyrd.jspwiki.tags.RequestResourceTag |