​<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​xsi:schemaLocation="http://www.exoplaform.org/xml/ns/kernel_1_2.xsd http://www.exoplaform.org/xml/ns/kernel_1_2.xsd" xmlns="http://www.exoplaform.org/xml/ns/kernel_1_2.xsd">
​ <external-component-plugins>
​     <!-- The full qualified name of the PortalContainerConfig -->
​     <target-component>org.exoplatform.container.definition.PortalContainerConfig</target-component>
​     <component-plugin>
​         <!-- The name of the plugin -->
​         <name>Add PortalContainer Definitions</name>
​         <!-- The name of the method to call on the PortalContainerConfig in order to register the PortalContainerDefinitions -->
​         <set-method>registerPlugin</set-method>
​         <!-- The full qualified name of the PortalContainerDefinitionPlugin -->
​         <type>org.exoplatform.container.definition.PortalContainerDefinitionPlugin</type>
​         <init-params>
​             <object-param>
​                 <name>portal</name>
​                 <object type="org.exoplatform.container.definition.PortalContainerDefinition">
​                     <!-- The name of the Portal Container: note that a Portal Container called "portal" 
​                          already exists in the default GateIn installation. Therefore, we actually redefine 
​                          that existing Portal Container here. -->
​                     <field name="name">
​                         <string>portal</string>
​                     </field>
​                     <!-- The name of the context name of the rest web application -->
​                     <field name="restContextName">
​                         <string>rest</string>
​                     </field>
​                     <!-- The name of the realm -->
​                     <field name="realmName">
​                         <string>gatein-domain</string>
​                     </field>
​                     <field name="externalSettingsPath">
​                         <string>configuration.properties</string>
​                     </field>
​                     <!--
​                         The list of all the context names that are needed to initialize the Portal Container properly.
​                         The order of the dependencies will define the initialization order and also the order for 
​                         loading resources. When a resource with the same path, say /dir/subdir/resource, is available 
​                         in more than one of the listed contexts, the one from the context closest to the end of this list 
​                         will be chosen. Here we want the resources available in gatein-portal-extension to win over all 
​                         other resources. Therefore we have added gatein-portal-extension as the last element of the list.
​                     -->
​                     <field name="dependencies">
​                         <collection type="java.util.ArrayList">
​                             <value>
​                                 <string>eXoResources</string>
​                             </value>
​                             <value>
​                                 <string>portal</string>
​                             </value>
​                             <value>
​                                 <string>dashboard</string>
​                             </value>
​                             <value>
​                                 <string>exoadmin</string>
​                             </value>
​                             <value>
​                                 <string>eXoGadgets</string>
​                             </value>
​                             <value>
​                                 <string>gwtGadgets</string>
​                             </value>
​                             <value>
​                                 <string>eXoGadgetServer</string>
​                             </value>
​                             <value>
​                                 <string>rest</string>
​                             </value>
​                             <value>
​                                <string>web</string>
​                             </value>
​                             <value>
​                                 <string>gatein-portal-extension</string>
​                             </value>
​                         </collection>
​                     </field>
​                 </object>
​             </object-param>
​         </init-params>
​     </component-plugin>
​ </external-component-plugins>
​</configuration>

​
​<node-navigation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_3 http://www.gatein.org/xml/ns/gatein_objects_1_3" xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_3">
​ <!-- Priority has no significance in site navigations. But it is required. See GTNPORTAL-2751 -->
​ <priority>1</priority>
​ 
​ <!-- 
​     In this file, we are adding a navigation node to the navigation of the site called "classic". 
​     The site-wide navigation is used e.g. in NavigationPortlet. 
​     Visibility of navigation nodes depends on <access-permissions> set in the sibling pages.xml file.
​     See also portal.configuration section of the file ../../portal-configuration.xml. 
​ -->
​ <page-nodes>
​     <node>
​         <name>page-just-added</name>
​         <!-- 
​             #{portal.extension.justAddedPage} is  place holder for an internationalized string.
​             See WEB-INF/classes/locale/navigation/portal/classic_en.properties
​         -->
​         <label>#{portal.extension.justAddedPage}</label>
​     </node>
​</page-nodes>
​</node-navigation>

​<page-set xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_3 http://www.gatein.org/xml/ns/gatein_objects_1_3"
​ xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_3">
​ <page>
​     <name>justAddedPage</name>
​     <title>Page Just Added</title>
​     <!-- This page and any navigation nodes refering to it will be visible to all visitors (signed in or anonymous). -->
​     <access-permissions>Everyone</access-permissions>
​     <edit-permission>*:/platform/administrators</edit-permission>
​     <portlet-application>
​         <portlet>
​             <application-ref>gatein-portal-extension</application-ref>
​             <portlet-ref>JustAddedPortlet</portlet-ref>
​         </portlet>
​         <title>Just Added Portlet</title>
​         <access-permissions>Everyone</access-permissions>
​         <show-info-bar>false</show-info-bar>
​         <show-application-state>false</show-application-state>
​         <show-application-mode>false</show-application-mode>
​     </portlet-application>
​ </page>
​</page-set>

​
​<node-navigation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_3 http://www.gatein.org/xml/ns/gatein_objects_1_3" xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_3">
​<!-- Priority is currently ignored for importMode merge. But it is required. See GTNPORTAL-2751 -->
​<priority>1</priority>
​
​<page-nodes>
​    <node>
​        <name>admins-sitemap</name>
​        <!-- 
​            #{platform.administrators.adminsSitemap} is  place holder for an internationalized string.
​            See WEB-INF/classes/locale/navigation/group/platform/administrators_en.properties
​        -->
​        <label>#{platform.administrators.adminsSitemap}</label>
​        <page-reference>group::/platform/administrators::adminsSitemap</page-reference>
​    </node>
​</page-nodes>
​</node-navigation>

​<page-set xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_3 http://www.gatein.org/xml/ns/gatein_objects_1_3"
​ xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_3">
​<!-- 
​    adminsSitemap page contains just SiteMapPortlet. There is nothing special about it. 
​    It is here just to demonstrate the adding of nodes to group navigation in the sibling 
​    navigation.xml file.
​-->
​<page>
​    <name>adminsSitemap</name>
​    <title>Admins' Sitemap</title>
​    <access-permissions>*:/platform/administrators</access-permissions>
​    <edit-permission>*:/platform/administrators</edit-permission>
​    <portlet-application>
​        <portlet>
​            <application-ref>web</application-ref>
​            <portlet-ref>SiteMapPortlet</portlet-ref>
​        </portlet>
​        <title>Sitemap</title>
​        <access-permissions>*:/platform/administrators</access-permissions>
​        <show-info-bar>false</show-info-bar>
​    </portlet-application>
​</page>
​</page-set>

​<node-navigation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_3 http://www.gatein.org/xml/ns/gatein_objects_1_3" xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_3">
​<!-- Priority has no significance in user navigations. But it is required. See GTNPORTAL-2751 -->
​<priority>1</priority>
​
​<page-nodes>
​    <node>
​        <name>roots-extra-dashboard</name>
​        <label>#{user.root.RootsExtraDashboard}</label>
​        <page-reference>user::root::roots-dashboard</page-reference>
​    </node>
​</page-nodes>
​</node-navigation>

​<page-set xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_objects_1_3 http://www.gatein.org/xml/ns/gatein_objects_1_3"
​xmlns="http://www.gatein.org/xml/ns/gatein_objects_1_3">
​<!-- 
​    roots-dashboard page contains just DashboardPortlet. There is nothing special about it. 
​    It is here just to demonstrate the adding of nodes to user navigation in the sibling 
​    navigation.xml file.
​-->
​<page>
​    <name>roots-dashboard</name>
​    <title>Root's Extra Dashboard</title>
​    <access-permissions>*:/platform/users</access-permissions>
​    <edit-permission>*:/platform/administrators</edit-permission>
​    <portlet-application>
​        <portlet>
​            <application-ref>dashboard</application-ref>
​            <portlet-ref>DashboardPortlet</portlet-ref>
​        </portlet>
​        <title>Root's Extra Dashboard</title>
​        <access-permissions>*:/platform/users</access-permissions>
​        <show-info-bar>false</show-info-bar>
​    </portlet-application>
​</page>
​</page-set>

​<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​xsi:schemaLocation="http://www.exoplaform.org/xml/ns/kernel_1_2.xsd http://www.exoplaform.org/xml/ns/kernel_1_2.xsd" xmlns="http://www.exoplaform.org/xml/ns/kernel_1_2.xsd">
​<external-component-plugins>
​    <!-- The full qualified name of the ResourceBundleService -->
​    <target-component>org.exoplatform.services.resources.ResourceBundleService</target-component>
​    <component-plugin>
​        <!-- The name of the plugin -->
​        <name>Sample ResourceBundle Plugin</name>
​        <!-- The name of the method to call on the ResourceBundleService in order to register the ResourceBundles -->
​        <set-method>addResourceBundle</set-method>
​        <!-- The full qualified name of the BaseResourceBundlePlugin -->
​        <type>org.exoplatform.services.resources.impl.BaseResourceBundlePlugin</type>
​        <init-params>
​            <values-param>
​                <name>init.resources</name>
​                <description>Initiate the following resources during the first launch.</description>
​                <value>locale.portal.extension</value>
​                <value>locale.navigation.user.root</value>
​                <!-- 
​                    Note that we actually do not need to name locale.navigation.portal.classic and 
​                    locale.navigation.group.platform.administrators here as they are in init.resources 
​                    of the default GateIn installation. But it makes no harm to include them once again here.
​                -->
​                <value>locale.navigation.portal.classic</value>
​                <value>locale.navigation.group.platform.administrators</value>
​           </values-param>
​        </init-params>
​    </component-plugin>

​<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
​xsi:schemaLocation="http://www.exoplatform.org/xml/ns/kernel_1_2.xsd http://www.exoplatform.org/xml/ns/kernel_1_2.xsd" xmlns="http://www.exoplatform.org/xml/ns/kernel_1_2.xsd">
​<external-component-plugins>
​    <!-- The full qualified name of the ResourceBundleService -->
​    <target-component>org.exoplatform.services.resources.ResourceBundleService</target-component>
​    <component-plugin>
​        <!-- The name of the plugin -->
​        <name>Sample ResourceBundle Plugin</name>
​        <!-- The name of the method to call on the ResourceBundleService in order to register the ResourceBundles -->
​        <set-method>addResourceBundle</set-method>
​        <!-- The full qualified name of the BaseResourceBundlePlugin -->
​        <type>org.exoplatform.services.resources.impl.BaseResourceBundlePlugin</type>
​        <init-params>
​            <values-param>
​                <name>init.resources</name>
​                <description>Initiate the following resources during the first launch.</description>
​                <value>locale.portal.extension</value>
​                <value>locale.navigation.user.root</value>
​                <!-- 
​                    Note that we actually do not need to name locale.navigation.portal.classic and 
​                    locale.navigation.group.platform.administrators here as they are in init.resources 
​                    of the default GateIn installation. But it makes no harm to include them once again here.
​                -->
​                <value>locale.navigation.portal.classic</value>
​                <value>locale.navigation.group.platform.administrators</value>
​            </values-param>
​            <values-param>
​                <name>portal.resource.names</name>
​                <description>These resources are merged to a single resource bundle which is accessible from anywhere 
​                    in GateIn. All these keys are located in the same bundle, which is separated from the navigation 
​                    resource bundles.</description>
​                <value>locale.portal.extension</value>
​            </values-param>
​        </init-params>
​    </component-plugin>
​</external-component-plugins>
​</configuration>

UIHomePagePortlet.Label.Slogan=Congratulations!
UIHomePagePortlet.Label.SubSlogan=You have just installed the GateIn Portal Extension
UIHomePagePortlet.Label.Title=Sign in as: