System Configuration

You can further customize a generated web application by setting some <context-param> values in the application’s web.xml file.

Name of Parameter in web.xml	Default Value	Purpose
`layout.fullPage`	`false`	This option is only relevant for the DESKTOP template: If set to `false`, the used `<p:layout>` is enclosed by `<h:panelGroup id="mainDiv" layout="block">` and the `fullPage` attribute of `<p:layout>` is set to `false`.
`layout.messagesPerPage`	`false`	Setting this to `true` activates a `<p:messages>` tag in the templates. The `<p:messages>` is part of template-embedded-north-center.xhtml. As a result of activating this, you will automatically get a means to show messages to a user of your application, without having to manually add a `<p:messages>` tag to every XHTML file of your application.
`layout.messagesSeverity`	“info,warn,error,fatal”	With this value, the attribute `severity` of `<p:messages>` is parameterized. Nominated the type of messages to be displayed.
`layout.messagesClosable`	`true`	Setting this to `false` prevent displayed messages from being closed by the user of the web application.
`layout.messagesShowDetail`	`true`	Setting this to `false` shows only the messages’ titles.
`layout.growlPerPage`	`false`	Setting this to `true` activates a `<p:growl>` tag in the templates. As a result of activating this, you will automatically get a means to show pop-up messages to a user of your application, without having to manually add a `<p:growl>` tag to every XHTML file of your application.
`layout.growlSeverity`	“info,warn,error,fatal”	With this value, the attribute `severity` of `<p:growl>` is parameterized. Nominated the type of messages to be displayed.
`layout.growlShowDetail`	`true`	Setting this to `false` shows only the messages’ titles.
`layout.growlDuration`	5000	Sets the number of milliseconds until a growl message automatically disappears from the web page.
`layout.globalTooltip`	`false`	Setting this to `true` adds a global `<p:tooltip>` to every page. Global tooltip uses the rendered `<p:tooltip>` for every JSF component that has a `title` attribute set. Ajax updates are supported as well, meaning if target component is updated with ajax, tooltip can still bind. As global tooltips are more efficient since only one instance of tooltip is used across all tooltip targets, it is suggested to be used instead of explicit tooltips unless you have a custom case e.g. different options, custom content. Note that you can also use `isGlobalTooltipUsed()` in AppLayoutCustomization.java to enable this functionality.