When SGML, forces the content-type to be text/html.
When XML, forces the content-type to be application/xhtml+xml.
When auto (the default), the following steps are performed to resolve the serialization:
Use the serialization active on the current request.
Use the application context-paramcom.aoapps.encoding.Serialization.default
that allows an application to control the selection of HTML versus XHTML.
When this context-param is unspecified or auto,
determine the serialization based on the client's Accept header.
This should normally be left with the default value of auto. This is used
when the content is known to contain invalid markup that can not be parsed as XML.
The <!DOCTYPE> to use,
must be one of default, HTML5, STRICT, TRANSITIONAL,
FRAMESET, or NONE.
Defaults to HTML5. NONE will suppress the output of a doctype.
When default, the following steps are performed to resolve the doctype:
Use the doctype active on the current request.
Use the application context-paramcom.aoapps.encoding.Doctype.default
that allows an application to control the default doctype.
When this context-param is unspecified or default,
defaults to HTML5.
When true, enables automatic newline (and tab indentation when enabled).
When false, disables automatic newline and tab indentation.
When auto (the default), the following steps are performed to resolve the autonli setting:
Use the autonli setting active on the current request.
Use the application context-paramcom.aoapps.html.servlet.DocumentEE.autonli
that allows an application to control the default autonli setting.
When this context-param is unspecified or auto,
defaults to false.
When true, enables tab indentation.
When false, disables tab indentation.
When auto (the default), the following steps are performed to resolve the indent setting:
Use the indent setting active on the current request.
Use the application context-paramcom.aoapps.html.servlet.DocumentEE.indent
that allows an application to control the default indent setting.
When this context-param is unspecified or auto,
defaults to false.
Each page may request a specific layout from the skin implementation. The currently
supported values are:
normal - This provides headers, footers, and full navigation.
This is the default layout if no layout is specified.
minimal - This provides a minimal layout without any page navigation
except headers and footers. This provides maximum area for the page content
while still maintaining a consistent look and feel.