gatein SVN: r8219 - in epp/docs/branches/5.2/User_Guide/en-US: modules/portal and 1 other directory.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-12-08 17:40:29 -0500 (Thu, 08 Dec 2011)
New Revision: 8219
Modified:
epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml
epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml
Log:
Further QE edits.
Modified: epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-12-08 21:51:37 UTC (rev 8218)
+++ epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-12-08 22:40:29 UTC (rev 8219)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>7</pubsnumber>
+ <pubsnumber>8</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and
Modified: epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-12-08 21:51:37 UTC (rev 8218)
+++ epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-12-08 22:40:29 UTC (rev 8219)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.0-8</revnumber>
+ <date>Fri Dec 9 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Further QE edits.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.0-7</revnumber>
<date>Thu Dec 8 2011</date>
<author>
Modified: epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml 2011-12-08 21:51:37 UTC (rev 8218)
+++ epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml 2011-12-08 22:40:29 UTC (rev 8219)
@@ -67,7 +67,7 @@
<term>Extended label mode</term>
<listitem>
<para>
- <remark>DOCS NOTE: I have no idea what this does.</remark>
+ This is a new feature which allows Administrators to add labels to nodes in multiple supported languages. When the language of the site is changed, the nodes will display the appropriate localized label.
</para>
</listitem>
</varlistentry>
Modified: epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml 2011-12-08 21:51:37 UTC (rev 8218)
+++ epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml 2011-12-08 22:40:29 UTC (rev 8219)
@@ -86,7 +86,7 @@
</step>
<step>
<para>
- Click on the <guilabel>Properties</guilabel> tab to fill in the <guilabel>Keep session alive</guilabel> property. There are 3 options:
+ Click on the <guilabel>Properties</guilabel> tab to fill in the <guilabel>Keep session alive</guilabel> property. There are three options:
<variablelist>
<varlistentry>
<term><emphasis role="bold">Never</emphasis></term>
@@ -117,7 +117,7 @@
</step>
<step>
<para>
- Also on the <guilabel>Properties</guilabel> tab, choose if you would like the portal to <guilabel>Show info bar by default</guilabel>. Check or uncheck this item as appropriate.
+ Also while on the <guilabel>Properties</guilabel> tab, check or uncheck the box labeled <guilabel>Show info bar by default</guilabel>. If checked, portlets show an information bar containing the portlet's name, a <emphasis>help</emphasis> drop-down menu and <guilabel>minimize/maximize</guilabel> buttons after being added to a page.
</para>
</step>
<step>
13 years
- 1
- 0
gatein SVN: r8218 - in epp/docs/branches/5.2/Reference_Guide/en-US: extras/Advanced_Development_JCR_lock-manager-config and 4 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-12-08 16:51:37 -0500 (Thu, 08 Dec 2011)
New Revision: 8218
Modified:
epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_lock-manager-config/you.xml
epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_PortalLifecycle/default160.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml
Log:
Further QE-related edits.
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>17</pubsnumber>
+ <pubsnumber>18</pubsnumber>
<abstract>
<para>
This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms.
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.0-18</revnumber>
+ <date>Fri Dec 9 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Further QE-related edits.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.0-17</revnumber>
<date>Thu Dec 8 2011</date>
<author>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_lock-manager-config/you.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_lock-manager-config/you.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_lock-manager-config/you.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -19,7 +19,7 @@
For another cache-loader class you should use another template with
cache-loader specific parameters
-->
- <loader class="org.jboss.cache.loader.JDBCCacheLoader" async=q"false" fetchPersistentState="false"
+ <loader class="org.jboss.cache.loader.JDBCCacheLoader" async="false" fetchPersistentState="false"
ignoreModifications="false" purgeOnStartup="false">
<properties>
cache.jdbc.table.name=${jbosscache-cl-cache.jdbc.table.name}
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_PortalLifecycle/default160.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_PortalLifecycle/default160.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_PortalLifecycle/default160.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -1,6 +1,6 @@
<servlet>
<servlet-name>GateInServlet</servlet-name>
- <servlet-class>org.gatein.wci.command.CommandServlet</servlet-class>
+ <servlet-class>org.gatein.wci.api.GateInServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -3,50 +3,60 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent">
%BOOK_ENTITIES;
]>
-<chapter id="chap-Reference_Guide-Portal_Life_cycle">
- <title>Portal Life-cycle</title>
- <section id="sect-Reference_Guide-Portal_Life_cycle-Overview">
- <title>Overview</title>
+ <chapter id="chap-Reference_Guide-Portal_Life_cycle">
+ <title>Portal Life-cycle</title>
+
+ <section id="sect-Reference_Guide-Portal_Life_cycle-Overview">
+ <title>Overview</title>
+
<para>
This chapter describes the portal life-cycle from the application server start to its stop including how requests are handled.
- </para>
-
- </section>
-
- <section id="sect-Reference_Guide-Portal_Life_cycle-Application_Server_start_and_stop">
- <title>Application Server start and stop</title>
+ </para>
+ </section>
+
+ <section id="sect-Reference_Guide-Portal_Life_cycle-Application_Server_start_and_stop">
+ <title>Application Server start and stop</title>
+
<para>
A portal instance is simply a set of web applications deployed as <filename>EAR</filename> and <filename>WAR</filename> archives. Portlets are also part of an enhanced WAR called a portlet application.
- </para>
+ </para>
+
<para>
JBoss Enterprise Portal Platform does not require any particular setup for your portlet in most common scenarios and the <filename>web.xml</filename> file can remain without any JBoss Enterprise Portal Platform specific configuration.
- </para>
+ </para>
+
<para>
During deployment, JBoss Enterprise Portal Platform will automatically and transparently inject a servlet into the portlet application to be able to interact with it. This feature is dependent on the underlying servlet container but will work out of the box on the proposed bundles.
- </para>
-
- </section>
-
- <!--
+ </para>
+ </section>
+<!--
TODO: Define the added listener
- --><!--
+ -->
+<!--
<section id="sect-Reference_Guide-Portal_Lifecycle-The_Listener">
<title>The Listener</title>
<para>
In the web.xml we can find servlet listener:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default158.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting> <!- ================================================================== ->
+</para> -->
+<!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default158.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -->
+<!-- <programlisting> <!- ================================================================== ->
<!- LISTENER ->
<!- ================================================================== ->
<listener>
<listener-class>org.exoplatform.portal.application.PortalSessionListener</listener-class>
</listener>
-</programlisting> --><!-- <para>
+</programlisting> -->
+<!-- <para>
That listener implements the HttpSessionListener which means it is called each time a session is created or destroyed; in other words, a session is created each time a user send a first request to the portal. That session is destroyed when he has not sent request to the portal for a long time or when he closes his browser.
</para>
-<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/PortalSessionListener.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>public class PortalSessionListener implements HttpSessionListener
-</programlisting> --><!-- <para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/PortalSessionListener.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -->
+<!-- <programlisting>public class PortalSessionListener implements HttpSessionListener
+</programlisting> -->
+<!-- <para>
Only the destroy method of the Listener object is implemented and it is used to flush resources when a user portal session expires. Here is the code:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default159.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting> /**
+</para> -->
+<!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default159.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -->
+<!-- <programlisting> /**
* This method is called when a HTTP session of a Portal instance is destroyed.
* By default the session time is 30 minutes.
*
@@ -81,103 +91,60 @@
}
}
</programlisting>
- --> <section id="sect-Reference_Guide-Portal_Life_cycle-The_Command_Servlet">
- <title>The Command Servlet</title>
+ -->
+ <section id="sect-Reference_Guide-Portal_Life_cycle-The_Command_Servlet">
+ <title>The Command Servlet</title>
+
<para>
The CommandServlet is called by the portlet container for requests to particular portlets, it also includes some <literal>init</literal> code when the portal is launched. This servlet (<literal>org.gatein.wci.api.GateInServlet</literal>) is automatically added during the deployment of each portlet application and mapped to <literal>/gateinservlet</literal>.
- </para>
+ </para>
+
<para>
This is equivalent to adding the following into <filename>web.xml</filename>.
- </para>
+ </para>
+
<note>
<title>Servlet Configuration</title>
- <para>
- <emphasis role="bold">As the servlet is already configured this example is for information only.</emphasis>
+
+ <para>
+ <emphasis role="bold">As the servlet is already configured this example is for information only.</emphasis>
</para>
-
- </note>
-
+ </note>
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_PortalLifecycle/default160.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <!-- <programlisting language="XML" role="XML"><![CDATA[<servlet>
-<servlet-name>GateInServlet</servlet-name>
-<servlet-class>org.gatein.wci.command.CommandServlet</servlet-class>
-<load-on-startup>0</load-on-startup>
-</servlet>
-<servlet-mapping>
-<servlet-name>GateInServlet</servlet-name>
-<url-pattern>/gateinservlet</url-pattern>
-</servlet-mapping>]]></programlisting> --> <para>
+ <para>
It is possible to filter on the <literal>GateInServlet</literal> by filtering the URL pattern used by the servlet mapping.
- </para>
+ </para>
+
<para>
The example below would create a servlet filter that calculates the time of execution of a portlet request.
- </para>
+ </para>
+
<para>
The filter class:
- </para>
-
+ </para>
<programlisting language="Java" role="Java"><xi:include href="../../extras/PortalDevelopment_PortalLifecycle/MyFilter.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <!-- <programlisting language="Java" role="JAVA"><![CDATA[package org.example;
-import java.io.IOException;
-import javax.servlet.FilterChain;
-import javax.servlet.FilterConfig;
-import javax.servlet.ServletException;
-import javax.servlet.ServletRequest;
-import javax.servlet.ServletResponse;
-public class MyFilter implements javax.servlet.Filter {
-public void doFilter(ServletRequest request, ServletResponse response,
-FilterChain chain) throws IOException, ServletException
-{
-long beforeTime = System.currentTimeMillis();
-chain.doFilter(request, response);
-long afterTime = System.currentTimeMillis();
-System.out.println("Time to execute the portlet request (in ms): " + (afterTime - beforeTime));
-}
-public void init(FilterConfig config) throws ServletException
-{
-}
-public void destroy()
-{
-}
-}
-]]></programlisting> --> <para>
+ <para>
The Java EE web application configuration file (<filename>web.xml</filename>) of the portlet is the file on which we want to know the time to serve a portlet request.
- </para>
+ </para>
+
<para>
As mentioned above nothing specific to JBoss Enterprise Portal Platform needs to be included, only the URL pattern to set has to be known.
- </para>
-
+ </para>
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_PortalLifecycle/default161.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <!-- <programlisting language="XML" role="XML"><![CDATA[<?xml version="1.0"?>
-<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
-version="2.5">
-<filter>
-<filter-name>MyFilter</filter-name>
-<filter-class>org.example.MyFilter</filter-class>
-</filter>
-<filter-mapping>
-<filter-name>MyFilter</filter-name>
-<url-pattern>/gateinservlet</url-pattern>
-<dispatcher>INCLUDE</dispatcher>
-</filter-mapping>
-</web-app>]]></programlisting> --> <para>
- <note>
- <title>INCLUDE dispatcher</title>
- <para>
- It is important to set <literal>INCLUDE</literal> as dispatcher as the portal will always hit the <literal>GateInServlet</literal> through a request dispatcher. Without this, the filter will not be triggered, unless direct access to a resource (such as an image) is set.
- </para>
-
- </note>
-
- </para>
-
- </section>
-
- <!--
-<para>
-Here is its definition in the web.xml file:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default162.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>
+ <note>
+ <title>INCLUDE dispatcher</title>
+
+ <para>
+ It is important to set <literal>INCLUDE</literal> as dispatcher as the portal will always hit the <literal>GateInServlet</literal> through a request dispatcher. Without this, the filter will not be triggered, unless direct access to a resource (such as an image) is set.
+ </para>
+ </note>
+ </section>
+<!--
+ <para>
+ Here is its definition in the web.xml file:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default162.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>
<servlet>
<servlet-name>portal</servlet-name>
<servlet-class>org.exoplatform.portal.application.PortalController</servlet-class>
@@ -187,9 +154,12 @@
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
-</programlisting> --><!-- <para>
-The load-on-startup tag tells that the init method of the servlet is called when the application server starts. We also define some configuration for the portal at the path WEB-INF/webui-configuration.xml inside the portal WAR.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/is1.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ The load-on-startup tag tells that the init method of the servlet is called when the application server starts. We also define some configuration for the portal at the path WEB-INF/webui-configuration.xml inside the portal WAR.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/is1.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* The PortalContainer servlet is the main entry point for the GateIn Portal product.
*
* Both the init() and service() methods are implemented. The first one is used to configure all the
@@ -239,11 +209,16 @@
log.info("Init of PortalController Servlet successful");
}
...
-</programlisting> --><!-- <para>
-We see that a PortalApplication class is instantiated, initialized and then referenced inside the WebAppController. Note that the WebAppController is a component located inside GateIn IoC service container (and hence registered in one of our service configuration XML file).
-</para> --><!-- <para>
-The <code><strong>PortalApplication</strong></code> extends the <code><strong>WebuiApplication</strong></code> which itself extends the <code><strong>Application</strong></code> abstract class.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/PortalApplication.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>public class PortalApplication extends WebuiApplication {
+</programlisting>
+ <para>
+ We see that a PortalApplication class is instantiated, initialized and then referenced inside the WebAppController. Note that the WebAppController is a component located inside GateIn IoC service container (and hence registered in one of our service configuration XML file).
+ </para>
+
+ <para>
+ The <code><strong>PortalApplication</strong></code> extends the <code><strong>WebuiApplication</strong></code> which itself extends the <code><strong>Application</strong></code> abstract class.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/PortalApplication.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>public class PortalApplication extends WebuiApplication {
protected static Log log = ExoLogger.getLogger("portal:PortalApplication");
final static public String PORTAL_APPLICATION_ID = "PortalApplication" ;
private ServletConfig sconfig_ ;
@@ -267,12 +242,16 @@
setResourceResolver(resolver) ;
}
...
-</programlisting> --><!-- <para>
-The main goal of this constructor is to fill an <code><strong>ApplicationResourceResolver</strong></code> with several <code><strong>ResourceResolver</strong></code> object that will allow the application to check for files such as groovy templates into different locations. Here the goal of the <code><strong>ResourceResolver</strong></code> is to abstract the different mechanisms to extract files from different location. In the previous code sample the <code><strong>ServletResourceResolver</strong></code> is used and hence methods based on the servlet context object are defined. Note that the <code><strong>ApplicationResourceResolver</strong></code> is also a class of type <code><strong>ResourceResolver</strong></code> but a special one as it can also contains several <code><strong>ResourceResolver</strong></cod!
e> itself.
-</para>
-<para>
-Then the <code><strong>onInit()</strong></code> method of the <code><strong>PortalApplication</strong></code> is called.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default163.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ The main goal of this constructor is to fill an <code><strong>ApplicationResourceResolver</strong></code> with several <code><strong>ResourceResolver</strong></code> object that will allow the application to check for files such as groovy templates into different locations. Here the goal of the <code><strong>ResourceResolver</strong></code> is to abstract the different mechanisms to extract files from different location. In the previous code sample the <code><strong>ServletResourceResolver</strong></code> is used and hence methods based on the servlet context object are defined. Note that the <code><strong>ApplicationResourceResolver</strong></code> is also a class of type <code><strong>ResourceResolver</strong></code> but a special one as it can also contains several <code><strong>ResourceResolver</strong>!
;</code> itself.
+ </para>
+
+ <para>
+ Then the <code><strong>onInit()</strong></code> method of the <code><strong>PortalApplication</strong></code> is called.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default163.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* This method first calls the super.onInit() of the WebuiApplication. That super method parse the XML
* file and stores its content in the ConfigurationManager object. It also set up he StateManager and
* init the application life-cycle phases.
@@ -288,12 +267,16 @@
applicationResourceBundleNames_[i] = applicationResourceBundleNames_[i].trim() ;
}
}
-</programlisting> --><!-- <para>
-The <code><strong>ConfigurationManager</strong></code> object parses the XML configuration file. The idea of the framework, once again, is to abstract the type of <code><strong>webapplication</strong></code> in used. Hence the <code><strong>webui-configuration.xml</strong></code> file is used by both the portal and portlet applications.
-</para>
-<para>
-Here is the <code><strong>webui-configuration</strong></code>:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default164.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting><webui-configuration>
+</programlisting>
+ <para>
+ The <code><strong>ConfigurationManager</strong></code> object parses the XML configuration file. The idea of the framework, once again, is to abstract the type of <code><strong>webapplication</strong></code> in used. Hence the <code><strong>webui-configuration.xml</strong></code> file is used by both the portal and portlet applications.
+ </para>
+
+ <para>
+ Here is the <code><strong>webui-configuration</strong></code>:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default164.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting><webui-configuration>
<application>
<init-params>
<param>
@@ -320,38 +303,48 @@
</events>
</application>
</webui-configuration>
-</programlisting> --><!-- <para>
-In the previous XML file we see that we define several tags such as:
-</para>
-<para>
-1.1.1 The ui-component-root
-</para>
-<para>
-Here it is the class <code><strong>org.exoplatform.portal.webui.workspace.UIPortalApplication</strong></code> which is a class that extends the <code><strong>UIApplication</strong></code> and hence is a sibling of <code><strong>UIPortletApplication</strong></code> (used by any GateIn Portlets as the Parent class to build the portlet component tree).
-</para>
-<para>
-The <code><strong>UIPortalApplication</strong></code> is responsible for building its subtrees - at request time according to some configuration parameters. If all components are displayed it is composed of 3 UI components:
-</para>
-<itemizedlist>
-<listitem>
-<para>
-<code><strong>UIControlWorkSpace</strong></code> : the left expandable column that can contains gadget containers and the start menu
-</para>
-</listitem>
-<listitem>
-<para>
-<code><strong>UIWorkingWorkSpace</strong></code>: the right part that can display the normal or webos portal layouts.
-</para>
-</listitem>
-<listitem>
-<para>
-<code><strong>UIPopupWindow</strong></code>: a popup window that display or not.
-</para>
-</listitem>
-</itemizedlist>
-<para>
-The <code><strong>UIPortalApplication</strong><code> constructor is shown next and is the starting point to build the UI Component tree to which Pages and Portlets will also be mounted. We will not describe that behavior here.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/is2.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ In the previous XML file we see that we define several tags such as:
+ </para>
+
+ <para>
+ 1.1.1 The ui-component-root
+ </para>
+
+ <para>
+ Here it is the class <code><strong>org.exoplatform.portal.webui.workspace.UIPortalApplication</strong></code> which is a class that extends the <code><strong>UIApplication</strong></code> and hence is a sibling of <code><strong>UIPortletApplication</strong></code> (used by any GateIn Portlets as the Parent class to build the portlet component tree).
+ </para>
+
+ <para>
+ The <code><strong>UIPortalApplication</strong></code> is responsible for building its subtrees - at request time according to some configuration parameters. If all components are displayed it is composed of 3 UI components:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <code><strong>UIControlWorkSpace</strong></code> : the left expandable column that can contains gadget containers and the start menu
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <code><strong>UIWorkingWorkSpace</strong></code>: the right part that can display the normal or webos portal layouts.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <code><strong>UIPopupWindow</strong></code>: a popup window that display or not.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The <code><strong>UIPortalApplication</strong><code> constructor is shown next and is the starting point to build the UI Component tree to which Pages and Portlets will also be mounted. We will not describe that behavior here.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/is2.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* The constructor of this class is used to build the tree of UI components that will be aggregated
* in the portal page.
*
@@ -405,42 +398,57 @@
setOwner(context.getPortalOwner());
}
...
-</programlisting> --><!-- <para>
-1.1.1 The StateManager
-</para>
-<para>
-The <code><strong>StateManager</strong></code> here is in the <code><strong>org.exoplatform.portal.application</strong></code> package which is an abstract class.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/StateManager.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>abstract public class StateManager {
+</programlisting>
+ <para>
+ 1.1.1 The StateManager
+ </para>
+
+ <para>
+ The <code><strong>StateManager</strong></code> here is in the <code><strong>org.exoplatform.portal.application</strong></code> package which is an abstract class.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/StateManager.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>abstract public class StateManager {
abstract public UIApplication restoreUIRootComponent(WebuiRequestContext context) throws Exception ;
abstract public void storeUIRootComponent(WebuiRequestContext context) throws Exception ;
abstract public void expire(String sessionId, WebuiApplication app) throws Exception ;
}
-</programlisting> --><!-- <para>
-The goal of the <code><strong>StateManager</strong></code> is to abstract the way <code><strong>UIApplication</strong></code> are stored and restored for all the user session lifetime. The expire method is called from the listener we have introduced before in this chapter.
-</para>
-<para>
-1.1.1 The application-life-cycle-listeners
-</para>
-<para>
-There are 2 life-cycle listeners in the Portal, one for the real business logic (<code><strong>PortalApplicationLifecycle</strong></code>), the other one for some monitoring issues. They both implement the interface <code><strong>ApplicationLifecycle<E extends RequestContext></strong></code>.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default165.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>public interface ApplicationLifecycle<E extends RequestContext> {
+</programlisting>
+ <para>
+ The goal of the <code><strong>StateManager</strong></code> is to abstract the way <code><strong>UIApplication</strong></code> are stored and restored for all the user session lifetime. The expire method is called from the listener we have introduced before in this chapter.
+ </para>
+
+ <para>
+ 1.1.1 The application-life-cycle-listeners
+ </para>
+
+ <para>
+ There are 2 life-cycle listeners in the Portal, one for the real business logic (<code><strong>PortalApplicationLifecycle</strong></code>), the other one for some monitoring issues. They both implement the interface <code><strong>ApplicationLifecycle<E extends RequestContext></strong></code>.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default165.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>public interface ApplicationLifecycle<E extends RequestContext> {
public void onInit(Application app) throws Exception ;
public void onStartRequest(Application app, E context) throws Exception ;
public void onEndRequest(Application app, E context) throws Exception ;
public void onDestroy(Application app) throws Exception ;
}
-</programlisting> --><!-- <para>
-Each registered life-cycle listener will then be able to get events when several states of the portal life-cycle are reached.
-</para>
-<para>
-1.1 The Request Handler
-</para>
-<para>
-Once started and fully configured, the portal application WAR can handle HTTP requests.
-</para>
-<para>
-The entry point is for sure the PortalController servlet we have already seen in the current chapter and defined in the <code><strong>web.xml</strong></code> of the portal context.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default166.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>...
+</programlisting>
+ <para>
+ Each registered life-cycle listener will then be able to get events when several states of the portal life-cycle are reached.
+ </para>
+
+ <para>
+ 1.1 The Request Handler
+ </para>
+
+ <para>
+ Once started and fully configured, the portal application WAR can handle HTTP requests.
+ </para>
+
+ <para>
+ The entry point is for sure the PortalController servlet we have already seen in the current chapter and defined in the <code><strong>web.xml</strong></code> of the portal context.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default166.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>...
/**
* This method simply delegates the incoming call to the WebAppController stored in the Portal Container object
*/
@@ -464,9 +472,12 @@
}
}
...
-</programlisting> --><!-- <para>
-The <code><strong>WebAppController</strong></code> is also a simple class on which several handlers can be bound. We have already seen that the <code><strong>PortalRequestHandler</strong></code> was already added in the init method of the servlet.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default167.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>...
+</programlisting>
+ <para>
+ The <code><strong>WebAppController</strong></code> is also a simple class on which several handlers can be bound. We have already seen that the <code><strong>PortalRequestHandler</strong></code> was already added in the init method of the servlet.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default167.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>...
/**
* The WebAppControler along with the PortalRequestHandler defined in the init() method of the
* PortalController servlet (controller.register(new PortalRequestHandler())) also add the
@@ -481,9 +492,12 @@
register(new CommandHandler()) ;
}
...
-</programlisting> --><!-- <para>
-Then the service method - modelled according to the servlet specification is called:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default168.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>...
+</programlisting>
+ <para>
+ Then the service method - modelled according to the servlet specification is called:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default168.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>...
/**
* This is the first method - in the GateIn web framework - reached by incoming HTTP request, it acts like a
* servlet service() method
@@ -523,9 +537,12 @@
}
}
...
-</programlisting> --><!-- <para>
-The handler in the portal case is the <code><strong>PortalRequestHandler</strong></code> which extends <code><strong>WebRequestHandler</strong></code> and that implement the abstract methods, mainly the execute() one.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/that.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ The handler in the portal case is the <code><strong>PortalRequestHandler</strong></code> which extends <code><strong>WebRequestHandler</strong></code> and that implement the abstract methods, mainly the execute() one.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/that.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* Created by The GateIn Platform SAS
* Mar 21, 2007
*
@@ -544,9 +561,12 @@
public void onDestroy(WebAppController controler) throws Exception {
}
}
-</programlisting> --><!-- <para>
-Here is the main class and the entire algorithm is described in the javadoc:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/handle.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ Here is the main class and the entire algorithm is described in the javadoc:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/handle.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* Created by The GateIn Platform SAS
* Dec 9, 2006
*
@@ -609,12 +629,16 @@
WebuiRequestContext.setCurrentInstance(null) ;
}
}
-</programlisting> --><!-- <para>
-The PortalRequestContext class is an important one as it is used in many places. The PortalRequestContext class wraps most of the request information. Accessing it from everywhere is quite simple as the object is stored in a ThreadLocal one, which means it bound to the current request thread. Hence a single call to WebuiRequestContext.getCurrentContext() will return the correct PortalRequestContext.
-</para>
-<para>
-As you can see, the PortalRequestContext extends the WebuiRequestContext one which also extends the abstract class RequestContext. Once again this hierarchy is to abstract the type of context in use , would it be a portal or portlet one.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/is3.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ The PortalRequestContext class is an important one as it is used in many places. The PortalRequestContext class wraps most of the request information. Accessing it from everywhere is quite simple as the object is stored in a ThreadLocal one, which means it bound to the current request thread. Hence a single call to WebuiRequestContext.getCurrentContext() will return the correct PortalRequestContext.
+ </para>
+
+ <para>
+ As you can see, the PortalRequestContext extends the WebuiRequestContext one which also extends the abstract class RequestContext. Once again this hierarchy is to abstract the type of context in use , would it be a portal or portlet one.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/is3.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* Created by The GateIn Platform SAS
* May 7, 2006
*
@@ -670,9 +694,12 @@
public static <T extends RequestContext> T getCurrentInstance() { return (T)tlocal_.get() ; }
public static void setCurrentInstance(RequestContext ctx) { tlocal_.set(ctx) ; }
}
-</programlisting> --><!-- <para>
-The WebuiRequestContext abstract class extends the RequestContext one and adds method for a Web environment such as accesses to the request and response objects or a list of components to update when using an Ajax call. More in the following header of the class:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/to.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>/**
+</programlisting>
+ <para>
+ The WebuiRequestContext abstract class extends the RequestContext one and adds method for a Web environment such as accesses to the request and response objects or a list of components to update when using an Ajax call. More in the following header of the class:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/to.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>/**
* Created by The GateIn Platform SAS
* May 7, 2006
*
@@ -740,12 +767,16 @@
public StateManager getStateManager() { return stateManager_; }
public void setStateManager(StateManager manager) { stateManager_ = manager ; }
}
-</programlisting> --><!-- <para>
-The PortalRequestContext mainly implements the abstract method already shown and only add few ones such as a reference to the portal owner or some information on the current navigation node path and the state of the portal (PUBLIC or PRIVATE ones)
-</para>
-<para>
-The PortalRequestHandler then tries to restore the UI component tree by calling the method restoreUIRootComponent(). The first time, there is nothing to restore and in that case the following part of code in the method is used:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/type.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting> if(state == null) {
+</programlisting>
+ <para>
+ The PortalRequestContext mainly implements the abstract method already shown and only add few ones such as a reference to the portal owner or some information on the current navigation node path and the state of the portal (PUBLIC or PRIVATE ones)
+ </para>
+
+ <para>
+ The PortalRequestHandler then tries to restore the UI component tree by calling the method restoreUIRootComponent(). The first time, there is nothing to restore and in that case the following part of code in the method is used:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/type.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting> if(state == null) {
synchronized(uiApplications) {
ConfigurationManager cmanager = app.getConfigurationManager() ;
String uirootClass = cmanager.getApplication().getUIRootComponent() ;
@@ -766,9 +797,12 @@
pcontainer.createSessionContainer(context.getSessionId(), uiApplication.getOwner()) ;
}
}
-</programlisting> --><!-- <para>
-The configuration manager object bound to the PortalApplication one is used to get the type for the root component which is then instanciated. the UserPortalConfig object - which is wrapper around the portal information for a given user - is also used and stored as an attribute in the PortalRequestContext. The UIPortalApplication is then created using the method createUIComponent() that is responsible of instanciating the component but also to configure it.
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default169.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting> public <T extends UIComponent> T createUIComponent(Class<T> type, String configId, String id, WebuiRequestContext context) throws Exception{
+</programlisting>
+ <para>
+ The configuration manager object bound to the PortalApplication one is used to get the type for the root component which is then instanciated. the UserPortalConfig object - which is wrapper around the portal information for a given user - is also used and stored as an attribute in the PortalRequestContext. The UIPortalApplication is then created using the method createUIComponent() that is responsible of instanciating the component but also to configure it.
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default169.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting> public <T extends UIComponent> T createUIComponent(Class<T> type, String configId, String id, WebuiRequestContext context) throws Exception{
Component config = configManager_.getComponentConfig(type, configId) ;
if(config == null) {
throw new Exception("Cannot find the configuration for the component " + type.getName() + ", configId " +configId) ;
@@ -778,9 +812,12 @@
config.getUIComponentLifecycle().init(uicomponent, context) ;
return type.cast(uicomponent) ;
}
-</programlisting> --><!-- <para>
-The ConfigurationManager method getComponentConfig() returns the Component object filled, it is a wrapper that contains all the information on the parameters for the class. Annotations are used to configure the instance as shown here:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default170.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting>@ComponentConfigs({
+</programlisting>
+ <para>
+ The ConfigurationManager method getComponentConfig() returns the Component object filled, it is a wrapper that contains all the information on the parameters for the class. Annotations are used to configure the instance as shown here:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default170.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting>@ComponentConfigs({
@ComponentConfig (
life-cycle = UIPortalApplicationLifecycle.class,
template = "system:/groovy/portal/webui/workspace/UIPortalApplication.gtmpl",
@@ -793,32 +830,40 @@
initParams = @ParamConfig( name = "public.showControlWorkspace", value = "false" )
)
})
-</programlisting> --><!-- <para>
-The processDecode() method of the UIPortalApplication is doing 3 actions:
-</para>
-<itemizedlist>
-<listitem>
-<para>
-if the nodePath is null (case of the first request) a call to super.processDecode(context) is made and we end the method here
-</para>
-</listitem>
-<listitem>
-<para>
-if the nodePath exist but is equals to the current one then we also call super and stops here
-</para>
-</listitem>
-<listitem>
-<para>
-if the requested nodePath is not equals to the current one , then an event of type PageNodeEvent.CHANGE<emphasis>PAGE</emphasis>NODE is sent to the asociated EventListener; a call to super is then done
-</para>
-</listitem>
-</itemizedlist>
-<para>
-The first case it simply does nothing. Note that the super.processDecode() goes up to the UIComponent which also calls the processDecode() method on the Lifecycle object that can be associated with the UIComponent
-</para>
-<para>
-The processAction() method of the UIPortalApplication is then called, as there is no method in the object itself it will call the processAction() of the UIPortalApplicationLifecycle bound to the UI component:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default171.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting> public void processAction(UIComponent uicomponent, WebuiRequestContext context) throws Exception {
+</programlisting>
+ <para>
+ The processDecode() method of the UIPortalApplication is doing 3 actions:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ if the nodePath is null (case of the first request) a call to super.processDecode(context) is made and we end the method here
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ if the nodePath exist but is equals to the current one then we also call super and stops here
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ if the requested nodePath is not equals to the current one , then an event of type PageNodeEvent.CHANGE<emphasis>PAGE</emphasis>NODE is sent to the asociated EventListener; a call to super is then done
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The first case it simply does nothing. Note that the super.processDecode() goes up to the UIComponent which also calls the processDecode() method on the Lifecycle object that can be associated with the UIComponent
+ </para>
+
+ <para>
+ The processAction() method of the UIPortalApplication is then called, as there is no method in the object itself it will call the processAction() of the UIPortalApplicationLifecycle bound to the UI component:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/default171.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting> public void processAction(UIComponent uicomponent, WebuiRequestContext context) throws Exception {
UIPortalApplication uiApp = (UIPortalApplication) uicomponent ;
String componentId = context.getRequestParameter(context.getUIComponentIdParameterName()) ;
if(componentId == null) return;
@@ -827,12 +872,16 @@
if(uiTarget == uicomponent) super.processAction(uicomponent, context) ;
uiTarget.processAction(context) ;
}
-</programlisting> --><!-- <para>
-If no uicomponent object is targeted, which is the case the first time (unless a bookmarked link is used) then nothing is done. Otherwise, the targeted component is extracted and a call of its processAction() method is executed.
-</para>
-<para>
-Then it is time to render the content and this is done inside the processRender() method. The method of the UIPortalApplication is shown here and it is the one that handles either full portal generation or AJAX request:
-</para> --><!-- <programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/it.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> --><!-- <programlisting> /**
+</programlisting>
+ <para>
+ If no uicomponent object is targeted, which is the case the first time (unless a bookmarked link is used) then nothing is done. Otherwise, the targeted component is extracted and a call of its processAction() method is executed.
+ </para>
+
+ <para>
+ Then it is time to render the content and this is done inside the processRender() method. The method of the UIPortalApplication is shown here and it is the one that handles either full portal generation or AJAX request:
+ </para>
+<programlisting language="Java" role="Java"><xi:include parse="text" href="../../extras/PortalDevelopment_PortalLifecycle/it.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+<programlisting> /**
* The processrender() method handles the creation of the returned HTML either for a full
* page render or in the case of an AJAX call
*
@@ -893,8 +942,6 @@
w.write("</div>") ;
}
}
-</programlisting> --><!-- </section>
-
- -->
-</chapter>
-
+</programlisting>
+-->
+ </chapter>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -156,7 +156,7 @@
<para>
If you are not going to use WSRP in JBoss Enterprise Portal Platform, it will not adversely affect your installation to leave it
- as-is. Otherwise, you can just remove the
+ as is. Otherwise, you can just remove the
<filename>gatein-wsrp-integration.ear</filename>
file from your AS deploy directory.
</para>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml 2011-12-08 10:36:22 UTC (rev 8217)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml 2011-12-08 21:51:37 UTC (rev 8218)
@@ -4,93 +4,93 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Reference_Guide-Framework_for_cross_domain_AJAX">
- <title>Framework for cross-domain AJAX</title>
- <para>
- (<ulink url="https://anonsvn.jboss.org/repos/exo-jcr/ws/trunk/exo.ws.frameworks.javasc...">https://anonsvn.jboss.org/repos/exo-jcr/ws/trunk/exo.ws.frameworks.javasc...</ulink>)
- </para>
- <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-Motivation">
- <title>Motivation</title>
- <para>
- XmlHttpRequest objects are bound by the same origin security policy of browsers, which prevents a page from accessing data from another server. This has put a serious limitation on Ajax developers: you can use XmlHttpRequests to make background calls to a server, but it has to be the same server that served up the current page. For more details, you can visit <ulink url="http://www.mozilla.org/projects/security/components/same-origin.html">http://www.mozilla.org/projects/security/components/same-origin.html</ulink>.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/ajax.gif" />
- </imageobject>
+ <title>Framework for cross-domain AJAX</title>
+ <para>
+ (<ulink url="https://anonsvn.jboss.org/repos/exo-jcr/ws/trunk/exo.ws.frameworks.javasc...">https://anonsvn.jboss.org/repos/exo-jcr/ws/trunk/exo.ws.frameworks.javasc...</ulink>)
+ </para>
+ <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-Motivation">
+ <title>Motivation</title>
+ <para>
+ XmlHttpRequest objects are bound by the same origin security policy of browsers, which prevents a page from accessing data from another server. This has put a serious limitation on Ajax developers: you can use XmlHttpRequests to make background calls to a server, but it has to be the same server that served up the current page. For more details, you can visit <ulink url="http://www.mozilla.org/projects/security/components/same-origin.html">http://www.mozilla.org/projects/security/components/same-origin.html</ulink>.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/ajax.gif" />
+ </imageobject>
- </mediaobject>
- <para>
- But actually writing client web applications that use this object can be tricky given restrictions imposed by web browsers on network connections across domains. So you need to find the way to bypass this limitation of AJAX.
- </para>
+ </mediaobject>
+ <para>
+ But actually writing client web applications that use this object can be tricky given restrictions imposed by web browsers on network connections across domains. So you need to find the way to bypass this limitation of AJAX.
+ </para>
- </section>
-
- <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-Scheme_how_it_works">
- <title>Scheme (how it works)</title>
- <para>
- To describe our method for cross-domain AJAX solution, let's consider the following scheme contains of 3 components:
- </para>
- <para>
- 1). User agent (a browser).
- </para>
- <para>
- 2). ServerA contains a main page with dedicated client and server IFRAMEs (see below) and an HTML client page (client.html) referenced from the client IFRAME. This client page contains dedicated script to push the data for request into server IFRAME.
- </para>
- <para>
- 3). ServerB contains remote service that want get access to and an HTML server page (server.html) referenced from the server IFRAME. This server page contains dedicated script to push the requested data into client IFRAME.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/eXoJCR/ajax-how-it-works.png" width="444" />
- </imageobject>
+ </section>
+
+ <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-Scheme_how_it_works">
+ <title>Scheme (how it works)</title>
+ <para>
+ To describe our method for cross-domain AJAX solution, let's consider the following scheme contains of 3 components:
+ </para>
+ <para>
+ 1). User agent (a browser).
+ </para>
+ <para>
+ 2). ServerA contains a main page with dedicated client and server IFRAMEs (see below) and an HTML client page (client.html) referenced from the client IFRAME. This client page contains dedicated script to push the data for request into server IFRAME.
+ </para>
+ <para>
+ 3). ServerB contains remote service that want get access to and an HTML server page (server.html) referenced from the server IFRAME. This server page contains dedicated script to push the requested data into client IFRAME.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/eXoJCR/ajax-how-it-works.png" width="444" />
+ </imageobject>
- </mediaobject>
+ </mediaobject>
- </section>
-
- <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-A_Working_Sequence">
- <title>A Working Sequence:</title>
- <para>
- 1) A Browser requests the Start page from the ServerA
- </para>
- <para>
- 2) The Start page is retrieved from the ServerA.
- </para>
- <para>
- 3) Create in the start page IFRAME (name it - "client iframe") and insert it in the document from ServerA (client.
- </para>
- <para>
- 4) In "client iframe" create ne IFRAME element ("server iframe") and insert it in the document from ServerB (server.html). Documents (client.html and server.html) contain special script that can transfer data between iframes.
- </para>
- <para>
- 5) "Client iframe" transfer information about HTTP method and URL that we want do cross-domain request to "server iframe".
- </para>
- <para>
- 6) "Server iframe" do simple XmlHttpRequest to the service that we need (it can do that because download from same domain) and get information from service.
- </para>
- <para>
- 7) "Server iframe" transfer data to "client iframe" and now we get information that we want.
- </para>
+ </section>
+
+ <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-A_Working_Sequence">
+ <title>A Working Sequence:</title>
+ <para>
+ 1) A Browser requests the Start page from the ServerA
+ </para>
+ <para>
+ 2) The Start page is retrieved from the ServerA.
+ </para>
+ <para>
+ 3) Create in the start page IFRAME (name it - "Client iFrame") and insert it in the document from ServerA (client.
+ </para>
+ <para>
+ 4) In "Client iFrame" create new IFRAME element ("Server iFrame") and insert it in the document from ServerB (server.html). Documents (client.html and server.html) contain special script that can transfer data between iFrames.
+ </para>
+ <para>
+ 5) "Client iFrame" transfer information about HTTP method and URL that we want do cross-domain request to "Server iFrame".
+ </para>
+ <para>
+ 6) "Server iFrame" do simple XmlHttpRequest to the service that we need (it can do that because download from same domain) and get information from service.
+ </para>
+ <para>
+ 7) "Server iFrame" transfer data to "Client iFrame" and now we get information that we want.
+ </para>
- </section>
-
- <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-How_to_use_it">
- <title>How to use it</title>
- <para>
- 1). Place the file client.html and xda.js on the serverA.
- </para>
- <para>
- 2). Place the file server.html on the serverB.
- </para>
- <para>
- 3). Declare xda.js in the main page.
- </para>
-
+ </section>
+
+ <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-How_to_use_it">
+ <title>How to use it</title>
+ <para>
+ 1). Place the file client.html and xda.js on the serverA.
+ </para>
+ <para>
+ 2). Place the file server.html on the serverB.
+ </para>
+ <para>
+ 3). Declare xda.js in the main page.
+ </para>
+
<programlisting language="HTML" role="HTML"><script type="text/javascript" src="xda.js"></script></programlisting>
- <para>
- 4). Create JS function which performs cross domain call as in the following example:
- </para>
-
+ <para>
+ 4). Create JS function which performs cross domain call as in the following example:
+ </para>
+
<programlisting language="Java" role="Java"><script type="text/javascript">
function test(){
var facade = xdaInit();
@@ -105,13 +105,13 @@
xda.create(facade);
}
</script></programlisting>
- <para>
- 5). Use this function (here it is bound to a button's onclick event).
- </para>
-
+ <para>
+ 5). Use this function (here it is bound to a button's onclick event).
+ </para>
+
<programlisting language="HTML" role="HTML"><button onclick='test()'>test cross-domain</button></programlisting>
- </section>
+ </section>
</chapter>
13 years
- 1
- 0
gatein SVN: r8217 - epp/portal/tags/EPP_5_2_0_GA/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component.
by do-not-reply＠jboss.org
Author: theute
Date: 2011-12-08 05:36:22 -0500 (Thu, 08 Dec 2011)
New Revision: 8217
Modified:
epp/portal/tags/EPP_5_2_0_GA/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java
Log:
JBEPP-1432: Paging of users in group is broken (ArrayIndexOutOfBoundsException)
Modified: epp/portal/tags/EPP_5_2_0_GA/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java
===================================================================
--- epp/portal/tags/EPP_5_2_0_GA/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java 2011-12-08 10:04:51 UTC (rev 8216)
+++ epp/portal/tags/EPP_5_2_0_GA/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java 2011-12-08 10:36:22 UTC (rev 8217)
@@ -20,6 +20,7 @@
package org.exoplatform.organization.webui.component;
import org.exoplatform.commons.utils.EmptySerializablePageList;
+import org.exoplatform.commons.utils.ListAccess;
import org.exoplatform.commons.utils.PageList;
import org.exoplatform.portal.webui.util.Util;
import org.exoplatform.services.organization.Group;
@@ -133,7 +134,9 @@
{
OrganizationService service = getApplicationComponent(OrganizationService.class);
MembershipHandler handler = service.getMembershipHandler();
- pageList = new FindMembershipByGroupPageList(group.getId(), 10);
+ ListAccess<?> list = handler.findAllMembershipsByGroup(group);
+ pageList = new FindMembershipByGroupPageList(group.getId(),
+ list.getSize() > 10 ? list.getSize() : 10);
}
UIGridUser uiGrid = getChild(UIGridUser.class);
pageList.setPageSize(5);
13 years
- 1
- 0
gatein SVN: r8216 - epp/portal/branches/EPP_5_2_Branch/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component.
by do-not-reply＠jboss.org
Author: theute
Date: 2011-12-08 05:04:51 -0500 (Thu, 08 Dec 2011)
New Revision: 8216
Modified:
epp/portal/branches/EPP_5_2_Branch/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java
Log:
JBEPP-1432: Paging of users in group is broken (ArrayIndexOutOfBoundsException)
Modified: epp/portal/branches/EPP_5_2_Branch/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java 2011-12-08 06:04:34 UTC (rev 8215)
+++ epp/portal/branches/EPP_5_2_Branch/portlet/exoadmin/src/main/java/org/exoplatform/organization/webui/component/UIUserInGroup.java 2011-12-08 10:04:51 UTC (rev 8216)
@@ -20,6 +20,7 @@
package org.exoplatform.organization.webui.component;
import org.exoplatform.commons.utils.EmptySerializablePageList;
+import org.exoplatform.commons.utils.ListAccess;
import org.exoplatform.commons.utils.PageList;
import org.exoplatform.portal.webui.util.Util;
import org.exoplatform.services.organization.Group;
@@ -133,7 +134,9 @@
{
OrganizationService service = getApplicationComponent(OrganizationService.class);
MembershipHandler handler = service.getMembershipHandler();
- pageList = new FindMembershipByGroupPageList(group.getId(), 10);
+ ListAccess<?> list = handler.findAllMembershipsByGroup(group);
+ pageList = new FindMembershipByGroupPageList(group.getId(),
+ list.getSize() > 10 ? list.getSize() : 10);
}
UIGridUser uiGrid = getChild(UIGridUser.class);
pageList.setPageSize(5);
13 years
- 1
- 0
gatein SVN: r8215 - in epp/docs/branches/5.2/Reference_Guide/en-US: modules/AuthenticationAndIdentity and 2 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-12-08 01:04:34 -0500 (Thu, 08 Dec 2011)
New Revision: 8215
Modified:
epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml
Log:
Adding remark tags for QE verification
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>16</pubsnumber>
+ <pubsnumber>17</pubsnumber>
<abstract>
<para>
This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms.
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -8,7 +8,7 @@
<simpara>
<revhistory>
<revision>
- <revnumber>5.2.0-16</revnumber>
+ <revnumber>5.2.0-17</revnumber>
<date>Thu Dec 8 2011</date>
<author>
<firstname>Scott</firstname>
@@ -17,7 +17,8 @@
</author>
<revdescription>
<simplelist>
- <member>Import GateIn WSRP content.</member>
+ <member>Re-import GateIn WSRP content.</member>
+ <member>Incorporate QE feedback (JBEPP-1431).</member>
</simplelist>
</revdescription>
</revision>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-Reference_Guide-PicketLink_IDM_integration">
- <title>PicketLink IDM integration</title>
+ <title><remark>PicketLink IDM integration</remark></title>
<para>
JBoss Enterprise Portal Platform uses the <literal>PicketLink IDM</literal> component to store necessary identity information about users, groups and memberships. While legacy interfaces are still used (<literal>org.exoplatform.services.organization</literal>) for identity management, there is a wrapper implementation that delegates to PicketLink IDM framework.
</para>
@@ -26,7 +26,7 @@
<para>
Additionally, <literal>org.exoplatform.services.organization</literal> <emphasis>membership</emphasis> concept needs to be translated into the IDM <emphasis>Role</emphasis> concept. Therefore <literal>PicketLink IDM</literal> model is used in a limited way. All these translations are applied by the integration layer.
</para>
-
+ <remark>The "Configuration Files" section has been commented out as the configuration parameters require more work than time allows before the 5.2.0 release.</remark>
<!--
DOCS NOTE: The content of this section are entirely wrong and needs to be rewritten. The config file in the first programlisting has been updated to the version in EPP 5.2.0, however time constraints prevented this from being actioned before the 5.2.0 GA release.
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Reference_Guide-Cluster_Configuration">
- <!-- This document was created with Syntext Serna Free. --> <title>Cluster Configuration</title>
+ <title>Cluster Configuration</title>
<section id="sect-Reference_Guide-Cluster_Configuration-Launching_Cluster">
<title>Launching Cluster</title>
<section id="sect-Reference_Guide-Launching_Cluster-Deploying_eXo_JCR_to_JBoss_Application_Server">
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Reference_Guide-JCR_configuration">
- <title>JCR configuration</title>
+ <title><remark>JCR configuration</remark></title>
<para>
The JCR configuration is defined in an XML file which is constructed as per the DTD below:
</para>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -104,51 +104,7 @@
</listitem>
</itemizedlist>
- <!-- <itemizedlist>
- <listitem>
- <para>
- MySQL 5.1 MYSQL Connector/J 5.1.8
- </para>
-
- </listitem>
- <listitem>
- <para>
- PostgresSQL 8.3.7 JDBC4 Driver, Version 8.3-605
- </para>
-
- </listitem>
- <listitem>
- <para>
- Oracle DB 11g (11.0.1.6), JDBC Driver Oracle 11g R1 (11.1.0.6.0)
- </para>
-
- </listitem>
- <listitem>
- <para>
- DB2 9,7 IBM Data Server Driver for JDBC and SQLJ (JCC Driver) v.9.1 (fixpack 3a)
- </para>
-
- </listitem>
- <listitem>
- <para>
- MS SQL Server 2005 SP3 JDBC Driver 2.0
- </para>
-
- </listitem>
- <listitem>
- <para>
- Sybase 15.0.3 Driver: Sybase jConnect JDBC driver v7 (Build 26502)
- </para>
-
- </listitem>
- <listitem>
- <para>
- HSQLDB (2.0.0)
- </para>
-
- </listitem>
-
- </itemizedlist> --> <note>
+ <note>
<title>Isolation Levels</title>
<para>
The JCR requires at least the <parameter>READ_COMMITED</parameter> isolation level and other RDBMS configurations can cause some side-effects and issues. So, please, make sure proper isolation level is configured on database server side.
@@ -386,7 +342,7 @@
</section>
<section id="sect-Reference_Guide-JDBC_Data_Container_Config-Multi_database_Configuration">
- <title>Multi-database Configuration</title>
+ <title><remark>Multi-database Configuration</remark></title>
<para>
You need to configure each workspace in a repository as part of multi-database configuration. Databases may reside on remote servers as required.
</para>
@@ -410,7 +366,7 @@
<itemizedlist>
<listitem>
<para>
- <parameter>driverClassName</parameter>, e.g. "org.hsqldb.jdbcDriver", "com.mysql.jdbc.Driver", "org.postgresql.Driver"
+ <parameter><remark>driverClassName</remark></parameter>, e.g. "org.hsqldb.jdbcDriver", "com.mysql.jdbc.Driver", "org.postgresql.Driver"
</para>
</listitem>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-12-08 05:53:14 UTC (rev 8214)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-12-08 06:04:34 UTC (rev 8215)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Reference_Guide-Search_Configuration">
- <title>Search Configuration</title>
+ <title><remark>Search Configuration</remark></title>
<para>
The search function in JCR can be configured to perform in specific ways. This section will discuss configuring the search function to improve search performance and results.
</para>
13 years
- 1
- 0
gatein SVN: r8214 - in epp/docs/branches/5.2/Reference_Guide/en-US: extras/Advanced_Development_JCR_external-value-storages and 4 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-12-08 00:53:14 -0500 (Thu, 08 Dec 2011)
New Revision: 8214
Modified:
epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_external-value-storages/default25.xml
epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_BackendConfiguration/default96.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml
Log:
JBEPP-1431: Incorporating QE feedback
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>15</pubsnumber>
+ <pubsnumber>16</pubsnumber>
<abstract>
<para>
This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms.
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -8,7 +8,7 @@
<simpara>
<revhistory>
<revision>
- <revnumber>5.2.0-15</revnumber>
+ <revnumber>5.2.0-16</revnumber>
<date>Thu Dec 8 2011</date>
<author>
<firstname>Scott</firstname>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_external-value-storages/default25.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_external-value-storages/default25.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Advanced_Development_JCR_external-value-storages/default25.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -1,4 +1,5 @@
-<value-storage id="Storage #1" class="org.exoplatform.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
+<value-storage id="Storage #1"
+class="org.exoplatform.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
<properties>
<property name="path" value="data/values"/>
</properties>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_BackendConfiguration/default96.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_BackendConfiguration/default96.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_BackendConfiguration/default96.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -1,6 +1,28 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+
+ Copyright (C) 2009 eXo Platform SAS.
+
+ This is free software; you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License as
+ published by the Free Software Foundation; either version 2.1 of
+ the License, or (at your option) any later version.
+
+ This software is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this software; if not, write to the Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
+
+-->
+
<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">
+ xsi:schemaLocation="http://www.exoplaform.org/xml/ns/kernel_1_1.xsd http://www.exoplaform.org/xml/ns/kernel_1_1.xsd"
+ xmlns="http://www.exoplaform.org/xml/ns/kernel_1_1.xsd">
<component>
@@ -8,6 +30,8 @@
<type>org.exoplatform.services.organization.idm.PicketLinkIDMCacheService</type>
</component>
+
+ <!-- non-clustered profile -->
<component>
<key>org.exoplatform.services.database.HibernateService</key>
<jmx-name>database:type=HibernateService</jmx-name>
@@ -18,6 +42,11 @@
<description>Default Hibernate Service</description>
<property name="hibernate.cache.region.jbc2.query.localonly" value="true" />
<property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.jbc2.MultiplexedJBossCacheRegionFactory" />
+ <!-- force usage of LOCAL cache configurations -->
+ <property name="hibernate.cache.region.jbc2.configs" value="picketlink-idm/idm-local-cache-config.xml" />
+ <property name="hibernate.cache.region.jbc2.cfg.entity" value="local-optimistic-entity" />
+ <property name="hibernate.cache.region.jbc2.cfg.ts" value="local-timestamps-cache" />
+
<property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" />
<property name="hibernate.show_sql" value="false"/>
<property name="hibernate.current_session_context_class" value="thread"/>
@@ -26,13 +55,41 @@
<property name="hibernate.connection.datasource" value="${gatein.idm.datasource.name}${container.name.suffix}"/>
<property name="hibernate.connection.autocommit" value="true"/>
<!--
- Should be automatically detected. Force otherwise
+ Should be automatically detected. Force otherwise
<property name="hibernate.dialect" value="org.hibernate.dialect.XXXDialect"/>
-->
</properties-param>
</init-params>
+ </component>
+
+ <!-- clustered profile -->
+ <component profiles="cluster">
+ <key>org.exoplatform.services.database.HibernateService</key>
+ <jmx-name>database:type=HibernateService</jmx-name>
+ <type>org.exoplatform.services.database.impl.HibernateServiceImpl</type>
+ <init-params>
+ <properties-param>
+ <name>hibernate.properties</name>
+ <description>Default Hibernate Service</description>
+ <property name="hibernate.cache.region.jbc2.query.localonly" value="true" />
+ <property name="hibernate.cache.region.jbc2.cachefactory" value="java:CacheManager"/>
+ <property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.jbc2.JndiMultiplexedJBossCacheRegionFactory" />
+ <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" />
+ <property name="hibernate.show_sql" value="false"/>
+ <property name="hibernate.current_session_context_class" value="thread"/>
+ <property name="hibernate.cache.use_second_level_cache" value="true"/>
+ <property name="hibernate.cache.use_query_cache" value="true"/>
+ <property name="hibernate.connection.datasource" value="${gatein.idm.datasource.name}${container.name.suffix}"/>
+ <property name="hibernate.connection.autocommit" value="true"/>
+ <!--
+ Should be automatically detected. Force otherwise
+ <property name="hibernate.dialect" value="org.hibernate.dialect.XXXDialect"/>
+ -->
+ </properties-param>
+ </init-params>
</component>
+
<component>
<key>org.exoplatform.services.organization.idm.PicketLinkIDMService</key>
<type>org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl</type>
@@ -42,16 +99,16 @@
<value>war:/conf/organization/picketlink-idm/picketlink-idm-config.xml</value>
<!--Sample LDAP config-->
- <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-LDAP-config.xml</value>-->
+ <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-ldap-config.xml</value>-->
<!--Read Only "ACME" LDAP Example-->
- <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-LDAP-acme-config.xml</value>-->
+ <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-ldap-acme-config.xml</value>-->
<!--OpenLDAP LDAP config-->
- <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-openLDAP-config.xml</value>-->
+ <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-openldap-config.xml</value>-->
<!--OpenLDAP ReadOnly "ACME" LDAP Example-->
- <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-openLDAP-acme-config.xml</value>-->
+ <!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-openldap-acme-config.xml</value>-->
<!--MSAD LDAP Example-->
<!--<value>war:/conf/organization/picketlink-idm/examples/picketlink-idm-msad-config.xml</value>-->
@@ -75,7 +132,7 @@
<value-param profiles="cluster">
<name>apiCacheConfig</name>
- <value>war:/conf/organization/picketlink-idm/jboss-cache-cluster.xml</value>
+ <value>war:/conf/organization/picketlink-idm/jboss-cache-api-cluster.xml</value>
</value-param>
<value-param>
@@ -85,8 +142,184 @@
<value-param profiles="cluster">
<name>storeCacheConfig</name>
- <value>war:/conf/organization/picketlink-idm/jboss-cache-cluster.xml</value>
+ <value>war:/conf/organization/picketlink-idm/jboss-cache-store-cluster.xml</value>
</value-param>
+
+ <value-param profiles="cluster">
+ <name>jgroups-configuration</name>
+ <value>${gatein.jcr.jgroups.config}</value>
+ </value-param>
+ <value-param profiles="cluster">
+ <name>jgroups-multiplexer-stack</name>
+ <value>false</value>
+ </value-param>
+
+ <value-param>
+ <name>cacheExpiration</name>
+ <value>1800000</value>
+ </value-param>
+
+
</init-params>
- </component>
\ No newline at end of file
+ </component>
+
+
+ <component>
+ <key>org.exoplatform.services.organization.OrganizationService</key>
+ <type>org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</type>
+ <init-params>
+ <object-param>
+ <name>configuration</name>
+ <object type="org.exoplatform.services.organization.idm.Config">
+ <!-- For all ids not mapped with type in 'groupTypeMappings' use parent id path
+ as a group type to store group in PicketLink IDM. The effect of setting
+ this option to false and not providing any mappings under 'groupTypeMappings' option
+ is that there can be only one group with a given name in all GateIn group tree-->
+ <field name="useParentIdAsGroupType">
+ <boolean>true</boolean>
+ </field>
+ <!-- Group stored in PicketLink IDM with a type mapped in 'groupTypeMappings' will
+ automatically be member under mapped parent. Normally groups are linked by
+ PicketLink IDM group association - such relationship won't be needed then. It can
+ be set to false if all groups are added via GateIn APIs
+ This option may be useful with LDAP config as it will make (if set to true) every entry
+ added to LDAP (not via GateIn management UI) appear in GateIn-->
+ <field name="forceMembershipOfMappedTypes">
+ <boolean>true</boolean>
+ </field>
+ <!-- When 'userParentIdAsGroupType is set to true this value will be used to
+ replace all "/" chars in id. This is because "/" is not allowed to be
+ used in group type name in PicketLink IDM-->
+ <field name="pathSeparator">
+ <string>.</string>
+ </field>
+ <!-- Name of a group stored in PicketLink IDM that acts as root group in GateIn - "/" -->
+ <field name="rootGroupName">
+ <string>GTN_ROOT_GROUP</string>
+ </field>
+ <!-- Map groups added with GateIn API as a childs of a given group ID to be stored with a given
+ group type name in PicketLink IDM. If parent ID ends with "/*" then all child groups will
+ have the mapped group type. Otherwise only direct (first level) children will use this type.
+
+ This can be leveraged by LDAP setup. Given LDAP DN configured in PicketLink IDM to
+ store specific group type will then store one given branch in GateIn group tree while
+ all other groups will remain in DB. -->
+ <field name="groupTypeMappings">
+ <map type="java.util.HashMap">
+ <entry>
+ <key><string>/</string></key>
+ <value><string>root_type</string></value>
+ </entry>
+
+ <!-- Uncomment for sample LDAP configuration -->
+ <!--
+ <entry>
+ <key><string>/platform/*</string></key>
+ <value><string>platform_type</string></value>
+ </entry>
+ <entry>
+ <key><string>/organization/*</string></key>
+ <value><string>organization_type</string></value>
+ </entry>
+ -->
+
+
+ <!-- Uncomment for ACME LDAP example -->
+ <!--
+ <entry>
+ <key><string>/acme/roles/*</string></key>
+ <value><string>acme_roles_type</string></value>
+ </entry>
+ <entry>
+ <key><string>/acme/organization_units/*</string></key>
+ <value><string>acme_ou_type</string></value>
+ </entry>
+ -->
+
+ <!-- Uncomment for MSAD ReadOnly LDAP example -->
+ <!--
+ <entry>
+ <key><string>/acme/roles/*</string></key>
+ <value><string>msad_roles_type</string></value>
+ </entry>
+ -->
+ </map>
+ </field>
+ <!-- If this option is used then each Membership created with MembrshipType that is
+ equal to value specified here will be stored in PicketLink IDM as simple
+ Group-User association-->
+ <field name="associationMembershipType">
+ <string>member</string>
+ </field>
+ <!-- if "associationMembershipType" option is used and this option is set to true
+ then Membership with MembershipType configured to be stored as PicketLink IDM association
+ will not be stored as PicketLink IDM Role -->
+ <field name="ignoreMappedMembershipType">
+ <boolean>false</boolean>
+ </field>
+ <!-- If 'true' will use JTA UserTransaction. If 'false' will use IDM transaction API -->
+ <field name="useJTA">
+ <boolean>false</boolean>
+ </field>
+
+ <!-- If PLIDM group will have name containing slash "/" char than it will be replace with following string.
+ Slashes are used in group paths and if present in names may cause unpredictable behaviour -->
+ <field name="slashReplacement">
+ <string>@_@_@</string>
+ </field>
+
+ <!-- If groups should be displayed in a sorted order in the management UI-->
+ <field name="sortGroups">
+ <boolean>true</boolean>
+ </field>
+
+ <!-- If memberships should be displayed in a sorted order in the management UI-->
+ <field name="sortMemberships">
+ <boolean>true</boolean>
+ </field>
+ </object>
+ </object-param>
+ </init-params>
+ </component>
+
+ <external-component-plugins>
+ <target-component>org.exoplatform.services.database.HibernateService</target-component>
+ <component-plugin>
+ <name>add.hibernate.mapping</name>
+ <set-method>addPlugin</set-method>
+ <type>org.exoplatform.services.database.impl.AddHibernateMappingPlugin</type>
+ <init-params>
+ <values-param>
+ <name>hibernate.mapping</name>
+ <value>picketlink-idm/mappings/HibernateRealm.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectCredentialBinaryValue.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectAttributeBinaryValue.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObject.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectCredential.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectCredentialType.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectAttribute.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectType.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectRelationship.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectRelationshipType.hbm.xml</value>
+ <value>picketlink-idm/mappings/HibernateIdentityObjectRelationshipName.hbm.xml</value>
+ </values-param>
+ <values-param profiles="sybase">
+ <name>hibernate.mapping</name>
+ <value>picketlink-idm/sybase-mappings/HibernateRealm.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectCredentialBinaryValue.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectAttributeBinaryValue.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObject.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectCredential.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectCredentialType.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectAttribute.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectType.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectRelationship.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectRelationshipType.hbm.xml</value>
+ <value>picketlink-idm/sybase-mappings/HibernateIdentityObjectRelationshipName.hbm.xml</value>
+ </values-param>
+ </init-params>
+ </component-plugin>
+ </external-component-plugins>
+
+</configuration>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -26,6 +26,12 @@
<para>
Additionally, <literal>org.exoplatform.services.organization</literal> <emphasis>membership</emphasis> concept needs to be translated into the IDM <emphasis>Role</emphasis> concept. Therefore <literal>PicketLink IDM</literal> model is used in a limited way. All these translations are applied by the integration layer.
</para>
+
+ <!--
+ DOCS NOTE: The content of this section are entirely wrong and needs to be rewritten. The config file in the first programlisting has been updated to the version in EPP 5.2.0, however time constraints prevented this from being actioned before the 5.2.0 GA release.
+
+ The section above notes that this document does not go into Picketlink IDM Config, so perhaps this section can remain hidden...
+
<section id="sect-Reference_Guide-PicketLink_IDM_integration-Configuration_Files">
<title>Configuration Files</title>
<para>
@@ -33,8 +39,8 @@
</para>
<programlistingco>
<areaspec>
- <area coords="6 90" id="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMServiceImpl" />
- <area coords="22 80" id="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMOrganizationServiceImpl" />
+ <area coords="95 80" id="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMServiceImpl" />
+ <area coords="170 80" id="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMOrganizationServiceImpl" />
</areaspec>
@@ -384,7 +390,7 @@
<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_BackendConfiguration/default97.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </section>
+ </section> -->
</section>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -106,10 +106,10 @@
</para>
<programlistingco>
<areaspec>
- <area coords="20" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-value_storages" />
- <area coords="27" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_cache" />
- <area coords="31" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_indexer" />
- <area coords="34" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_lock_manager" />
+ <area coords="20 80" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-value_storages" />
+ <area coords="26 80" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_cache" />
+ <area coords="31 80" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_indexer" />
+ <area coords="34 80" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_lock_manager" />
</areaspec>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -8,6 +8,47 @@
<para>
The JCR configuration is defined in an XML file which is constructed as per the DTD below:
</para>
+<programlisting language="XML" role="XML"><!ELEMENT repository-service (repositories)>
+<!ATTLIST repository-service default-repository NMTOKEN #REQUIRED>
+<!ELEMENT repositories (repository)>
+<!ELEMENT repository (security-domain,access-control,session-max-age,authentication-policy,workspaces)>
+<!ATTLIST repository
+ default-workspace NMTOKEN #REQUIRED
+ name NMTOKEN #REQUIRED
+ system-workspace NMTOKEN #REQUIRED
+>
+<!ELEMENT security-domain (#PCDATA)>
+<!ELEMENT access-control (#PCDATA)>
+<!ELEMENT session-max-age (#PCDATA)>
+<!ELEMENT authentication-policy (#PCDATA)>
+<!ELEMENT workspaces (workspace+)>
+<!ELEMENT workspace (container,initializer,cache,query-handler)>
+<!ATTLIST workspace name NMTOKEN #REQUIRED>
+<!ELEMENT container (properties,value-storages)>
+<!ATTLIST container class NMTOKEN #REQUIRED>
+<!ELEMENT value-storages (value-storage+)>
+<!ELEMENT value-storage (properties,filters)>
+<!ATTLIST value-storage class NMTOKEN #REQUIRED>
+<!ELEMENT filters (filter+)>
+<!ELEMENT filter EMPTY>
+<!ATTLIST filter property-type NMTOKEN #REQUIRED>
+<!ELEMENT initializer (properties)>
+<!ATTLIST initializer class NMTOKEN #REQUIRED>
+<!ELEMENT cache (properties)>
+<!ATTLIST cache
+ enabled NMTOKEN #REQUIRED
+ class NMTOKEN #REQUIRED
+>
+<!ELEMENT query-handler (properties)>
+<!ATTLIST query-handler class NMTOKEN #REQUIRED>
+<!ELEMENT access-manager (properties)>
+<!ATTLIST access-manager class NMTOKEN #REQUIRED>
+<!ELEMENT lock-manager (time-out,persister)>
+<!ELEMENT time-out (#PCDATA)>
+<!ELEMENT persister (properties)>
+<!ELEMENT properties (property+)>
+<!ELEMENT property EMPTY></programlisting>
+
<section id="sect-Reference_Guide-JCR_configuration-Portal_configuration">
<title>Portal configuration</title>
<para>
@@ -737,48 +778,6 @@
</listitem>
</varlistentry>
</variablelist>
-
-<programlisting language="XML" role="XML"><!ELEMENT repository-service (repositories)>
-<!ATTLIST repository-service default-repository NMTOKEN #REQUIRED>
-<!ELEMENT repositories (repository)>
-<!ELEMENT repository (security-domain,access-control,session-max-age,authentication-policy,workspaces)>
-<!ATTLIST repository
- default-workspace NMTOKEN #REQUIRED
- name NMTOKEN #REQUIRED
- system-workspace NMTOKEN #REQUIRED
->
-<!ELEMENT security-domain (#PCDATA)>
-<!ELEMENT access-control (#PCDATA)>
-<!ELEMENT session-max-age (#PCDATA)>
-<!ELEMENT authentication-policy (#PCDATA)>
-<!ELEMENT workspaces (workspace+)>
-<!ELEMENT workspace (container,initializer,cache,query-handler)>
-<!ATTLIST workspace name NMTOKEN #REQUIRED>
-<!ELEMENT container (properties,value-storages)>
-<!ATTLIST container class NMTOKEN #REQUIRED>
-<!ELEMENT value-storages (value-storage+)>
-<!ELEMENT value-storage (properties,filters)>
-<!ATTLIST value-storage class NMTOKEN #REQUIRED>
-<!ELEMENT filters (filter+)>
-<!ELEMENT filter EMPTY>
-<!ATTLIST filter property-type NMTOKEN #REQUIRED>
-<!ELEMENT initializer (properties)>
-<!ATTLIST initializer class NMTOKEN #REQUIRED>
-<!ELEMENT cache (properties)>
-<!ATTLIST cache
- enabled NMTOKEN #REQUIRED
- class NMTOKEN #REQUIRED
->
-<!ELEMENT query-handler (properties)>
-<!ATTLIST query-handler class NMTOKEN #REQUIRED>
-<!ELEMENT access-manager (properties)>
-<!ATTLIST access-manager class NMTOKEN #REQUIRED>
-<!ELEMENT lock-manager (time-out,persister)>
-<!ELEMENT time-out (#PCDATA)>
-<!ELEMENT persister (properties)>
-<!ELEMENT properties (property+)>
-<!ELEMENT property EMPTY></programlisting>
-
</section>
<!-- <section id="sect-Reference_Guide-Portal_configuration-Help_application_to_prohibit_the_use_of_closed_sessions">
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -34,8 +34,8 @@
</para>
<programlistingco>
<areaspec>
- <area coords="1" id="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-id" />
- <area coords="3" id="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-path" />
+ <area coords="1 80" id="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-id" />
+ <area coords="3 80" id="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-path" />
</areaspec>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -410,7 +410,7 @@
<itemizedlist>
<listitem>
<para>
- <parameter>driverliteral</parameter>, e.g. "org.hsqldb.jdbcDriver", "com.mysql.jdbc.Driver", "org.postgresql.Driver"
+ <parameter>driverClassName</parameter>, e.g. "org.hsqldb.jdbcDriver", "com.mysql.jdbc.Driver", "org.postgresql.Driver"
</para>
</listitem>
@@ -567,7 +567,7 @@
</step>
<step>
<para>
- Remove parameter <parameter>source-name</parameter> and add next lines instead. Describe your values for a JDBC driver, database UR: and username.
+ Remove parameter <parameter>source-name</parameter> and add next lines instead. Describe your values for a JDBC driver, database URL and username.
</para>
</step>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-12-08 04:53:12 UTC (rev 8213)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-12-08 05:53:14 UTC (rev 8214)
@@ -20,7 +20,7 @@
<programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default61.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- The table below outlines the Configuration Parameters available, their default setting, which version of eXo JCR they were implemented in and other useful information:
+ The table below outlines <emphasis role="bold">some</emphasis> of the Configuration Parameters available, their default setting, which version of eXo JCR they were implemented in and other useful information (further parameters are explained in <xref linkend="sect-Reference_Guide-JBoss_Cache_configuration-Indexer_lock_manager_and_data_container_configuration"/>):
</para>
<table id="tabl-Reference_Guide-Search_Configuration-Configuration_parameters">
<!-- align="left" pgwide="1" --> <title>Configuration parameters</title>
13 years
- 1
- 0
gatein SVN: r8213 - epp/docs/branches/5.2/User_Guide/en-US/images.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-12-07 23:53:12 -0500 (Wed, 07 Dec 2011)
New Revision: 8213
Added:
epp/docs/branches/5.2/User_Guide/en-US/images/PageSelectorEmpty.png
Log:
Adding new image suggested by QE feedback
Added: epp/docs/branches/5.2/User_Guide/en-US/images/PageSelectorEmpty.png
===================================================================
(Binary files differ)
Property changes on: epp/docs/branches/5.2/User_Guide/en-US/images/PageSelectorEmpty.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
13 years
- 1
- 0
gatein SVN: r8212 - in epp/docs/branches/5.2/User_Guide: en-US and 3 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-12-07 23:52:24 -0500 (Wed, 07 Dec 2011)
New Revision: 8212
Modified:
epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/User_Guide/en-US/images/AddNode4.png
epp/docs/branches/5.2/User_Guide/en-US/images/Calculator.png
epp/docs/branches/5.2/User_Guide/en-US/images/Calendar.png
epp/docs/branches/5.2/User_Guide/en-US/images/CodePaste.png
epp/docs/branches/5.2/User_Guide/en-US/images/EditLayout2.png
epp/docs/branches/5.2/User_Guide/en-US/images/EditNavigation.png
epp/docs/branches/5.2/User_Guide/en-US/images/EditPortal2.6New.png
epp/docs/branches/5.2/User_Guide/en-US/images/NewGadget.png
epp/docs/branches/5.2/User_Guide/en-US/images/PortalProperties.png
epp/docs/branches/5.2/User_Guide/en-US/images/PortalSetting2.5.png
epp/docs/branches/5.2/User_Guide/en-US/images/RSSReader.png
epp/docs/branches/5.2/User_Guide/en-US/images/Todo.png
epp/docs/branches/5.2/User_Guide/en-US/modules/account/Register_New_Accounts.xml
epp/docs/branches/5.2/User_Guide/en-US/modules/account/Sign_in_and_Sign_out.xml
epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml
epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml
epp/docs/branches/5.2/User_Guide/publican.cfg
Log:
JBEPP-1431: Action QA feedback.
Modified: epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-12-08 04:52:24 UTC (rev 8212)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>6</pubsnumber>
+ <pubsnumber>7</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and
Modified: epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-12-08 04:52:24 UTC (rev 8212)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.0-7</revnumber>
+ <date>Thu Dec 8 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Action QA feedback.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.0-6</revnumber>
<date>Tue Nov 15 2011</date>
<author>
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/AddNode4.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/Calculator.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/Calendar.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/CodePaste.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/EditLayout2.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/EditNavigation.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/EditPortal2.6New.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/NewGadget.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/PortalProperties.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/PortalSetting2.5.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/RSSReader.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/images/Todo.png
===================================================================
(Binary files differ)
Modified: epp/docs/branches/5.2/User_Guide/en-US/modules/account/Register_New_Accounts.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/modules/account/Register_New_Accounts.xml 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/en-US/modules/account/Register_New_Accounts.xml 2011-12-08 04:52:24 UTC (rev 8212)
@@ -4,175 +4,175 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Register_New_Accounts">
- <title>Register New Accounts</title>
- <para>
- Unregistered users visiting a portal in public mode are limited in the content they can see.
- </para>
- <para>
- Users who need access to deeper content or who need to perform actions within the portal should register themselves and then contact the portal administrator to gain appropriate access permissions to their account.
- </para>
- <para>
- Users can quickly and easily register a new account for themselves.
- </para>
- <procedure>
- <step>
- <para>
- Click <emphasis role="bold">Register</emphasis> on the Navigation bar.
- </para>
+ <title><remark>Register New Accounts</remark></title>
+ <para>
+ Unregistered users visiting a portal in public mode are limited in the content they can see.
+ </para>
+ <para>
+ Users who need access to deeper content or who need to perform actions within the portal should register themselves and then contact the portal administrator to gain appropriate access permissions to their account.
+ </para>
+ <para>
+ Users can quickly and easily register a new account for themselves.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Click <emphasis role="bold">Register</emphasis> on the Navigation bar.
+ </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Register.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Register.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- <para>
- The <emphasis role="bold">Register New Account</emphasis> page appears:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/AccountSetting.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/AccountSetting.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
- </imageobject>
- </mediaobject>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Register.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Register.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ <para>
+ The <emphasis role="bold">Register New Account</emphasis> page appears:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/AccountSetting.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/AccountSetting.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
+ </imageobject>
+ </mediaobject>
- <para>
- Complete the form with the required information:
- </para>
+ <para>
+ Complete the form with the required information:
+ </para>
- <variablelist>
- <varlistentry>
- <term><emphasis role="bold">User Name</emphasis></term>
- <listitem>
- <para>
- The name used to log in. This username must be between 3 and 30 characters long. Click the magnifying glass icon beside the user name to check whether the chosen username is available.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Password</emphasis></term>
- <listitem>
- <para>
- The password must be between 6 and 30 characters and can contain spaces.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Confirm Password</emphasis></term>
- <listitem>
- <para>
- Re-type the password above. The <emphasis>Password</emphasis> and <emphasis>Confirm Password</emphasis> fields must be the same.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">First Name</emphasis></term>
- <listitem>
- <para>
- The user's first name. This name must be between 3 and 45 characters long.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Last Name</emphasis></term>
- <listitem>
- <para>
- The user's last name. This name must also be between 3 and 45 characters long.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Email Address</emphasis></term>
- <listitem>
- <para>
- The user's email address. This must be in the appropriate format. For example: <replaceable>username(a)abc.com</replaceable>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </step>
- <step>
- <para>
- Enter the text displayed at <literal>Text Validation</literal> into the empty field below it:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Verification.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Verification.png" format="PNG" align="center" contentwidth="90mm" />
- </imageobject>
- </mediaobject>
- </step>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis role="bold">User Name</emphasis></term>
+ <listitem>
+ <para>
+ The name used to log in. This username must be between 3 and 30 characters long, start with a character. Only alpha, digit, underscore, dash and dot characters are allowed for the username. Click the magnifying glass icon beside the user name to check whether the chosen username is available.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Password</emphasis></term>
+ <listitem>
+ <para>
+ The password must be between 6 and 30 characters and can contain spaces.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Confirm Password</emphasis></term>
+ <listitem>
+ <para>
+ Re-type the password above. The <emphasis>Password</emphasis> and <emphasis>Confirm Password</emphasis> fields must be the same.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">First Name</emphasis></term>
+ <listitem>
+ <para>
+ The user's first name. This name must be between 1 and 45 characters long.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Last Name</emphasis></term>
+ <listitem>
+ <para>
+ The user's last name. This name must also be between 1 and 45 characters long.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Email Address</emphasis></term>
+ <listitem>
+ <para>
+ The user's email address. This must be in the appropriate format. For example: <replaceable>username(a)abc.com</replaceable>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </step>
+ <step>
+ <para>
+ Enter the text displayed at <literal>Text Validation</literal> into the empty field below it:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Verification.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Verification.png" format="PNG" align="center" contentwidth="90mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
-<!-- <step>
- <para>
- Input values in the <emphasis role="bold">User Profile</emphasis> tab, include: Profile information, Home information, Business information. These fields are not required.
- </para>
- <para>
- JBoss Enterprise Portal Platform facilitates four commonly used languagues: English, French, Vietnamese and Arabic in the <emphasis role="bold">Language</emphasis> field. You can select one of these languages to work with.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/UserProfile.png" format="PNG" align="center" width="444" />
- </imageobject>
- </mediaobject>
- </step> -->
- <step>
- <para>
- Click <emphasis role="bold">Subscribe</emphasis> to register a new account or <emphasis role="bold">Reset</emphasis> to refresh all entered values. You cannot add a new account if one of the following cases occurs:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The chosen <emphasis role="bold">User name</emphasis> already exists or is invalid.
- </para>
- </listitem>
- <listitem>
- <para>
- The <emphasis role="bold">User name</emphasis> has less than 3 characters or more than 30 characters.
- </para>
- </listitem>
- <listitem>
- <para>
- The <emphasis role="bold">Password</emphasis> has less than 6 characters or more than 30 characters.
- </para>
- </listitem>
- <listitem>
- <para>
- The <emphasis role="bold">Password</emphasis> and <emphasis role="bold">Confirm Password</emphasis> fields are not the same.
- </para>
- </listitem>
- <listitem>
- <para>
- The <emphasis role="bold">Email Address</emphasis> format is not valid.
- </para>
- </listitem>
- <listitem>
- <para>
- The <emphasis role="bold">text verification</emphasis> is not correct.
- </para>
- </listitem>
- <listitem>
- <para>
- A required field (or fields) is empty.
- </para>
- </listitem>
- </itemizedlist>
- </step>
- </procedure>
- <para>
- After adding a new account, you should contact the administrator to set appropriate permissions on your account.
- <note>
- <para>
- Be sure you enter your email address carefully. Should you forget your user name or password, you can recover it from this email address.
- </para>
- </note>
- </para>
+<!-- <step>
+ <para>
+ Input values in the <emphasis role="bold">User Profile</emphasis> tab, include: Profile information, Home information, Business information. These fields are not required.
+ </para>
+ <para>
+ JBoss Enterprise Portal Platform facilitates four commonly used languagues: English, French, Vietnamese and Arabic in the <emphasis role="bold">Language</emphasis> field. You can select one of these languages to work with.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/UserProfile.png" format="PNG" align="center" width="444" />
+ </imageobject>
+ </mediaobject>
+ </step> -->
+ <step>
+ <para>
+ Click <emphasis role="bold">Subscribe</emphasis> to register a new account or <emphasis role="bold">Reset</emphasis> to refresh all entered values. You cannot add a new account if one of the following cases occurs:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The chosen <emphasis role="bold">User name</emphasis> already exists or is invalid.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <emphasis role="bold">User name</emphasis> has less than 3 characters or more than 30 characters.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <emphasis role="bold">Password</emphasis> has less than 6 characters or more than 30 characters.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <emphasis role="bold">Password</emphasis> and <emphasis role="bold">Confirm Password</emphasis> fields are not the same.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <emphasis role="bold">Email Address</emphasis> format is not valid.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <emphasis role="bold">text verification</emphasis> is not correct.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A required field (or fields) is empty.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ </procedure>
+ <para>
+ After adding a new account, you should contact the administrator to set appropriate permissions on your account.
+ <note>
+ <para>
+ Be sure you enter your email address carefully. Should you forget your user name or password, you can recover it from this email address.
+ </para>
+ </note>
+ </para>
</section>
Modified: epp/docs/branches/5.2/User_Guide/en-US/modules/account/Sign_in_and_Sign_out.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/modules/account/Sign_in_and_Sign_out.xml 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/en-US/modules/account/Sign_in_and_Sign_out.xml 2011-12-08 04:52:24 UTC (rev 8212)
@@ -4,13 +4,13 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Sign_In_and_Sign_Out">
- <title>Sign In and Sign Out</title>
+ <title><remark>Sign In and Sign Out</remark></title>
- <para>
- In order to enter the portal in private mode, you should use the account previously registered.
- </para>
- <para>
- To sign in to a portal, users must complete the <emphasis role="bold">Sign in</emphasis> form:
+ <para>
+ In order to enter the portal in private mode, you should use the account previously registered.
+ </para>
+ <para>
+ To sign in to a portal, users must complete the <emphasis role="bold">Sign in</emphasis> form:
</para>
<mediaobject>
<imageobject role="html">
@@ -22,141 +22,141 @@
</mediaobject>
<para>
This form contains the following elements:
- </para>
- <variablelist>
- <varlistentry>
- <term>
- <emphasis role="bold">User name</emphasis>
- </term>
- <listitem>
- <para>
- The registered user name.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <emphasis role="bold">Password</emphasis>
- </term>
- <listitem>
- <para>
- The registered password.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <emphasis role="bold">Remember My Login</emphasis>
- </term>
- <listitem>
- <para>
- Check this box to avoid log in every time
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <emphasis role="bold">Forgot your User Name/Password?</emphasis>
- </term>
- <listitem>
- <para>
- To follow some steps to get the forgotten user name or password. Please refer to <xref linkend="sect-User_Guide-Account_and_Password_Retrieval"/> for more details.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <emphasis role="bold">Sign in</emphasis>
- </term>
- <listitem>
- <para>
- To sign into JBoss Enterprise Portal Platform with user name and password.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <emphasis role="bold">Discard</emphasis>
- </term>
- <listitem>
- <para>
- Close the Sign In form without logging in.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>
+ <emphasis role="bold">User name</emphasis>
+ </term>
+ <listitem>
+ <para>
+ The registered user name.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <emphasis role="bold">Password</emphasis>
+ </term>
+ <listitem>
+ <para>
+ The registered password.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <emphasis role="bold">Remember My Login</emphasis>
+ </term>
+ <listitem>
+ <para>
+ Check this box to avoid log in every time
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <emphasis role="bold">Forgot your User Name/Password?</emphasis>
+ </term>
+ <listitem>
+ <para>
+ To follow some steps to get the forgotten user name or password. Please refer to <xref linkend="sect-User_Guide-Account_and_Password_Retrieval"/> for more details.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <emphasis role="bold">Sign in</emphasis>
+ </term>
+ <listitem>
+ <para>
+ To sign into JBoss Enterprise Portal Platform with user name and password.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <emphasis role="bold">Discard</emphasis>
+ </term>
+ <listitem>
+ <para>
+ Close the Sign In form without logging in.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<section id="sect-User_Guide-Sign_In">
- <title>Sign In</title>
- <procedure>
- <step>
- <para>
- Go to your portal by entering the URL into the address bar of your browser (For example <emphasis role="bold">http://localhost:8080/portal</emphasis>).
- </para>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Sign in</emphasis> link at the top right of the page if you are current in the Classic portal. The <emphasis role="bold">Sign in</emphasis> form appears.
- </para>
- </step>
- <step>
- <para>
- Input your registered <emphasis role="bold">User name</emphasis> and <emphasis role="bold">Password</emphasis> .
- </para>
- </step>
- <step>
- <para>
- Select the <emphasis role="bold">Remember My Login</emphasis> check box when you sign in JBoss Enterprise Portal Platform at the first time if you want to automatically return to JBoss Enterprise Portal Platform without signing in again. You can see <xref linkend="sect-User_Guide-Remember_User_Account" /> for more details.
- </para>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Sign in</emphasis> button to submit the form or <emphasis role="bold">Discard</emphasis> to escape.
- </para>
- </step>
- </procedure>
- <para>
- If the user name does not exist or the user name and/or password is invalid an alert message will appear. To attempt the log in again; click the <emphasis role="bold">OK</emphasis> button on the alert message to be returned to the Sign In form. Enter the user name and password again.
- </para>
- <para>
- After signing in, you will be redirected to the homepage and welcomed with your full name in the top right corner of the page.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Toolbar.png" format="PNG" align="center" scale="110"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Toolbar.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
+ <title>Sign In</title>
+ <procedure>
+ <step>
+ <para>
+ Go to your portal by entering the URL into the address bar of your browser (For example <emphasis role="bold">http://localhost:8080/portal</emphasis>).
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Sign in</emphasis> link at the top right of the page if you are current in the Classic portal. The <emphasis role="bold">Sign in</emphasis> form appears.
+ </para>
+ </step>
+ <step>
+ <para>
+ Input your registered <emphasis role="bold">User name</emphasis> and <emphasis role="bold">Password</emphasis> .
+ </para>
+ </step>
+ <step>
+ <para>
+ Select the <emphasis role="bold">Remember My Login</emphasis> check box when you sign in JBoss Enterprise Portal Platform at the first time if you want to automatically return to JBoss Enterprise Portal Platform without signing in again. You can see <xref linkend="sect-User_Guide-Remember_User_Account" /> for more details.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Sign in</emphasis> button to submit the form or <emphasis role="bold">Discard</emphasis> to escape.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ If the user name does not exist or the user name and/or password is invalid you will be redirected to the GateIn Sign In form. Enter a correct user name and password.
+ </para>
+ <para>
+ After signing in, you will be redirected to the homepage and welcomed with your full name in the top right corner of the page.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Toolbar.png" format="PNG" align="center" scale="110"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Toolbar.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
</section>
<section id="sect-User_Guide-Sign_Out">
- <title>Sign Out</title>
- <para>
- This feature ends the authenticated session and returns the user to the anonymous portal.
- </para>
- <procedure>
- <step>
- <para>
- In the upper left corner of the screen, hover your cursor over the JBoss Enterprise Portal Platform icon. A drop down menu will appear.
- </para>
- </step>
- <step>
- <para>
- Click <emphasis role="bold">Sign out</emphasis> :
- </para>
- </step>
- </procedure>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/StarPortlet.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/StarPortlet.png" format="PNG" align="center" scalefit="1" contentwidth="130mm"/>
- </imageobject>
- </mediaobject>
+ <title>Sign Out</title>
+ <para>
+ This feature ends the authenticated session and returns the user to the anonymous portal.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ In the upper left corner of the screen, hover your cursor over the JBoss Enterprise Portal Platform icon. A drop down menu will appear.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click <emphasis role="bold">Sign out</emphasis> :
+ </para>
+ </step>
+ </procedure>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/StarPortlet.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/StarPortlet.png" format="PNG" align="center" scalefit="1" contentwidth="130mm"/>
+ </imageobject>
+ </mediaobject>
</section>
Modified: epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Navigation_Nodes.xml 2011-12-08 04:52:24 UTC (rev 8212)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Manage_Navigation_Nodes">
- <title>Manage Navigation Nodes</title>
+ <title><remark>Manage Navigation Nodes</remark></title>
<para>
If you are the portal administrator (or the administrator has granted you the appropriate permission privileges) you can execute all actions related to portal nodes. These actions include adding new nodes or editing, copying, moving, deleting or cloning existing nodes.
</para>
@@ -31,7 +31,7 @@
</step>
<step>
<para>
- Right-click on the selected navigation or node and select <emphasis role="bold">Add new Node</emphasis> option. The <emphasis role="bold">Add new node</emphasis> form appears:
+ Right-click on the selected navigation or node and select <guilabel>Add Node</guilabel> option. The <guilabel>ADD/EDIT PAGE NODE</guilabel> form appears:
</para>
<mediaobject>
<imageobject role="html">
@@ -59,11 +59,27 @@
<term><emphasis role="bold">Node name</emphasis></term>
<listitem>
<para>
- The name of the node. This field is required and must be unique. Only alpha, digit and underscore characters are allowed for this field and it must have at least 3 characters.
+ The name of the node. This field is required and must be unique. Only alpha, digit, dash and underscore characters are allowed for this field and it must be between 3 and 30 characters.
</para>
</listitem>
</varlistentry>
<varlistentry>
+ <term>Extended label mode</term>
+ <listitem>
+ <para>
+ <remark>DOCS NOTE: I have no idea what this does.</remark>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Language</term>
+ <listitem>
+ <para>
+ Set the language for the node.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
<term><emphasis role="bold">Label</emphasis></term>
<listitem>
<para>
@@ -109,10 +125,10 @@
</para>
<mediaobject>
<imageobject role="html">
- <imagedata fileref="images/PageSelector.png" format="PNG" align="center" scale="110" />
+ <imagedata fileref="images/PageSelectorEmpty.png" format="PNG" align="center" scale="110" />
</imageobject>
<imageobject role="fo">
- <imagedata fileref="images/PageSelector.png" format="PNG" align="center" contentwidth="150mm"/>
+ <imagedata fileref="images/PageSelectorEmpty.png" format="PNG" align="center" contentwidth="150mm"/>
</imageobject>
</mediaobject>
<variablelist>
@@ -183,7 +199,7 @@
</para>
<para>
- Or, enter values into both fields to futher limit your search results by both
+ Or, enter values into both fields to further limit your search results by both
<emphasis role="bold">Title</emphasis>
and <emphasis role="bold">Site Name</emphasis>.
</para>
@@ -223,6 +239,14 @@
<emphasis role="bold">Page Selector</emphasis>
form.
</para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/PageSelector.png" format="PNG" align="center" scale="110" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/PageSelector.png" format="PNG" align="center" contentwidth="150mm"/>
+ </imageobject>
+ </mediaobject>
<para>
After configuring the page node settings, the page selector and the node's icon, click the
<emphasis role="bold">Save</emphasis>
Modified: epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/en-US/modules/portal/Manage_Portals.xml 2011-12-08 04:52:24 UTC (rev 8212)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Manage_Portals">
- <title>Manage Portals</title>
+ <title><remark>Manage Portals</remark></title>
<section id="sect-User_Guide-Create_a_New_Portal">
@@ -61,7 +61,7 @@
Click the next <emphasis role="bold">Portal Setting</emphasis> tab to configure some aspects of the new portal.
</para>
<para>
- Enter a string for the <emphasis role="bold">Portal Name</emphasis> field. This field is required and must be unique. Only alphabetical, numerical and underscore characters are allowed for this field and the name must have at least 3 characters.
+ Enter a string for the <emphasis role="bold">Portal Name</emphasis> field. This field is required and must be unique. Only alphabetical, numerical, dash and underscore characters are allowed for this field and the name must be between 3 and 30 characters.
</para>
</step>
<step>
@@ -71,12 +71,22 @@
</step>
<step>
<para>
+ Enter a Label for the new portal. This field is optional.
+ </para>
+ </step>
+ <step>
+ <para>
+ Enter a description of the portal. This field is optional.
+ </para>
+ </step>
+ <step>
+ <para>
Select a skin for a portal.
</para>
</step>
<step>
<para>
- Click on the <emphasis role="bold">Properties</emphasis> tab to fill in the <emphasis role="bold">Keep session alive</emphasis> property. There are 3 options:
+ Click on the <guilabel>Properties</guilabel> tab to fill in the <guilabel>Keep session alive</guilabel> property. There are 3 options:
<variablelist>
<varlistentry>
<term><emphasis role="bold">Never</emphasis></term>
@@ -107,6 +117,11 @@
</step>
<step>
<para>
+ Also on the <guilabel>Properties</guilabel> tab, choose if you would like the portal to <guilabel>Show info bar by default</guilabel>. Check or uncheck this item as appropriate.
+ </para>
+ </step>
+ <step>
+ <para>
Click on the <emphasis role="bold">Permission Setting</emphasis> tab and set the permissions for the Portal.
</para>
<itemizedlist>
@@ -201,7 +216,7 @@
<note>
<title>Custom Portlets</title>
<para>
- If you want to include a custom portlet or gadget on a page, you may wish to refer to the <emphasis>JBoss Portlet Tools User Guide</emphasis> in the JBoss Developer Studio documentation (<ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/"></ulink>) and/or the <emphasis role="bold">Portlet development</emphasis> section of the <emphasis>JBoss Enterprise Portal Platform Reference Guide</emphasis> (<ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.1"></ulink>) for more information about creating and deploying portlets.
+ If you want to include a custom portlet or gadget on a page, you may wish to refer to the <emphasis>JBoss Portlet Tools User Guide</emphasis> in the JBoss Developer Studio documentation (<ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/"></ulink>) and/or the <emphasis role="bold">Portlet development</emphasis> section of the <emphasis>JBoss Enterprise Portal Platform Reference Guide</emphasis> (<ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/"></ulink>) for more information about creating and deploying portlets.
</para>
</note>
</section>
Modified: epp/docs/branches/5.2/User_Guide/publican.cfg
===================================================================
--- epp/docs/branches/5.2/User_Guide/publican.cfg 2011-12-08 04:49:36 UTC (rev 8211)
+++ epp/docs/branches/5.2/User_Guide/publican.cfg 2011-12-08 04:52:24 UTC (rev 8212)
@@ -5,7 +5,7 @@
type: Book
brand: JBoss
debug:1
-#show_remarks: 1
+show_remarks: 1
cvs_branch: DOCS-RHEL-6
cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
cvs_pkg: JBoss_Enterprise_Portal_Platform-User_Guide-5.2-web-__LANG__
\ No newline at end of file
13 years
- 1
- 0
gatein SVN: r8211 - in epp/docs/branches/5.2/Site_Publisher/Release_Notes: en-US and 1 other directory.
by do-not-reply＠jboss.org
Author: jaredmorgs
Date: 2011-12-07 23:49:36 -0500 (Wed, 07 Dec 2011)
New Revision: 8211
Modified:
epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml
epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg
Log:
Rebrewed book with CVE notes added and Support links section updated
Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-12-08 04:49:17 UTC (rev 8210)
+++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-12-08 04:49:36 UTC (rev 8211)
@@ -42,6 +42,15 @@
</listitem>
</itemizedlist>
</chapter>
+ <chapter id="Release_Notes-Installation">
+ <title>Installation</title>
+ <para>
+ The JBoss Site Publisher <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements.
+ </para>
+ <para>
+ The <citetitle>Installation Guide</citetitle> can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>.
+ </para>
+ </chapter>
<chapter id="Release_Notes-Component_Features">
<title>Component Features</title>
<formalpara>
@@ -69,71 +78,38 @@
</varlistentry>
</variablelist>
</chapter>
- <chapter>
- <title>New Features</title>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="XML"/>
- </chapter>
<chapter id="Release_Notes-Documentation">
<title>Documentation</title>
<para>
An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location.
</para>
</chapter>
- <chapter id="Release_Notes-Installation">
- <title>Installation</title>
- <para>
- The JBoss Site Publisher <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements.
- </para>
- <para>
- The <citetitle>Installation Guide</citetitle> can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>.
- </para>
- </chapter>
- <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_">
- <title> Product Support and License Website Links </title>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes">
- <title>Support Processes</title>
+ <chapter>
+ <title> Product Support Links </title>
+ <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes_1">
+ <title>Product Update and Support Processes</title>
<para>
- <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
+ <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</ulink>
</para>
</formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_">
- <title> Production Support Scope of Coverage </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
+ <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage__1">
+ <title> Developer Support Scope of Coverage, and Service Level Agreement</title>
+ <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink>
+
</para>
</formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_">
- <title> Production Support Service Level Agreement </title>
+ <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement__1">
+ <title>Certified and Compatible Configurations</title>
<para>
- <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
+ <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink>
</para>
</formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_">
- <title> Developer Support Scope of Coverage </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_">
- <title> Developer Support Service Level Agreement </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_">
- <title> Product Update and Support Policy by Product </title>
- <para>
- <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_">
- <title> JBoss End User License Agreement </title>
- <para>
- <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
- </para>
- </formalpara>
</chapter>
<chapter>
+ <title>New Features</title>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="XML"/>
+ </chapter>
+ <chapter>
<title>
<remark>NEEDINFO</remark>
</title>
Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg 2011-12-08 04:49:17 UTC (rev 8210)
+++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg 2011-12-08 04:49:36 UTC (rev 8211)
@@ -7,4 +7,4 @@
show_remarks: 1
cvs_branch: DOCS-RHEL-6
cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
-cvs_pkg: JBoss_Enterprise_Portal_Platform-Site_Publisher_5.2.0_BETA_Release_Notes-5.2-web-__LANG__
+cvs_pkg: JBoss_Enterprise_Portal_Platform-Site_Publisher_5.2.0_Release_Notes-5.2-web-__LANG__
13 years
- 1
- 0
gatein SVN: r8210 - in epp/docs/branches/5.2/Release_Notes: en-US and 1 other directory.
by do-not-reply＠jboss.org
Author: jaredmorgs
Date: 2011-12-07 23:49:17 -0500 (Wed, 07 Dec 2011)
New Revision: 8210
Modified:
epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml
epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml
epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
epp/docs/branches/5.2/Release_Notes/publican.cfg
Log:
Rebrewed book with CVE notes added and Support links section updated
Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-08 04:49:17 UTC (rev 8210)
@@ -188,6 +188,33 @@
<para>For detailed information about component versions included in this release, refer to <xref linkend="Release_Notes-Component_Features"/></para>
</note>
</chapter>
+ <chapter id="Release_Notes-Documentation">
+ <title>Documentation</title>
+ <para>
+ An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location.
+ </para>
+ </chapter>
+ <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_">
+ <title> Product Support Links </title>
+ <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes">
+ <title>Product Update and Support Processes</title>
+ <para>
+ <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</ulink>
+ </para>
+ </formalpara>
+ <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_">
+ <title> Developer Support Scope of Coverage, and Service Level Agreement</title>
+ <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink>
+
+ </para>
+ </formalpara>
+ <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_">
+ <title>Certified and Compatible Configurations</title>
+ <para>
+ <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink>
+ </para>
+ </formalpara>
+ </chapter>
<chapter>
<title>New Features</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="XML"/>
@@ -218,56 +245,5 @@
<para>
Stuff about migration from 5.1.0 to 5.1.1.
</para>
- </chapter>--> <chapter id="Release_Notes-Documentation">
- <title>Documentation</title>
- <para>
- An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location.
- </para>
- </chapter>
- <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_">
- <title> Product Support and License Website Links </title>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes">
- <title>Support Processes</title>
- <para>
- <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_">
- <title> Production Support Scope of Coverage </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_">
- <title> Production Support Service Level Agreement </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_">
- <title> Developer Support Scope of Coverage </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_">
- <title> Developer Support Service Level Agreement </title>
- <para>
- <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_">
- <title> Product Update and Support Policy by Product </title>
- <para>
- <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink>
- </para>
- </formalpara>
- <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_">
- <title> JBoss End User License Agreement </title>
- <para>
- <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink>
- </para>
- </formalpara>
- </chapter>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
+ </chapter>--> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
</book>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-12-08 04:49:17 UTC (rev 8210)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>8</pubsnumber>
+ <pubsnumber>10</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Enterprise Portal Platform &VZ; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product.
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2011-12-08 04:49:17 UTC (rev 8210)
@@ -8,8 +8,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>5.2.0-8</revnumber>
- <date>Mon Dec 05 2011</date>
+ <revnumber>5.2.0-10</revnumber>
+ <date>Thu Dec 08 2011</date>
<author>
<firstname>Jared</firstname>
<surname>Morgan</surname>
@@ -17,7 +17,7 @@
</author>
<revdescription>
<simplelist>
- <member>Third Draft of Enterprise Portal Platform 5.2.0 Release Notes, considered to be the final draft before GA.</member>
+ <member>Third Draft respin of Enterprise Portal Platform 5.2.0 Release Notes, with changes to Product Support Links and some CVE XSS issues. This is considered to be the final draft before GA.</member>
</simplelist>
</revdescription>
</revision>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml 2011-12-08 04:49:17 UTC (rev 8210)
@@ -1,340 +1,502 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version='1.0'?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
+
+
<variablelist>
-<!-- https://issues.jboss.org/browse/JBEPP-736 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-736 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack.
-</para>
- <note>
- <para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.
+<note><para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para></note>
</para>
- </note>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-932 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-932 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
URL handler support is available in this release. The WCM component uses this feature to support locales as part of the URL.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-933 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-933 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Performance bottlenecks have been removed when a portal runs with hundreds of navigation nodes.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-934 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-934 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In previous releases, navigation node translations had to be managed in language property files. This release allows Navigation nodes to be translated directly through the administration interface.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-937 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-937 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
It is now possible to define a portlet.xml that describes elements such as filters that need to be applied to all portlets. The file is located in jboss-as/server/[configuration]/conf/gatein/portlet.xml
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-938 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-938 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
This release upgrades Shindig to version 2.0.2. Shindig is used to embed OpenSocial gadgets. Refer to the Component Versions section for the definitive version featured in this release.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-939 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-939 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Web service security between WSRP producers and consumers is available in this release. This enhancement allows for encrypted communication and access to authenticated user content over WSRP.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-940 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940</ulink>
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-940 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
This release makes it possible to configure several LDAP servers containing different users with GateIn. In a ReadOnly scenario, the user is searched in all configured sources. In a ReadWrite scenario, the user is created only in the first configured LDAP server, but obtained from all.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1008 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1008 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
Application registry categories are now cached for better performance.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1015 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1015 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Each site can now have a site description, which can be accessed and used by the management applications.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1016 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1016 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1045 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045</ulink>
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1045 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
WSRP was previously unavailable for portal extensions. The new WSRP component now properly initializes itself even when started from an extension (as opposed to the default portal container).
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1077 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077</ulink>
- </term>
- <listitem>
- <remark>This issue is unassigned!</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1077 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077</ulink></term>
+ <listitem>
+
+ <remark>This issue is unassigned!</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The datasource for JCR is now using managed transactions, and required a change in the datasource descriptor.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1078 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1078 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
EPP is now partially available in Czech language.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1088 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1088 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
When adding a page to a site, pages are displayed in a drop-down list instead of a free form text field. This makes adding pages more intuitive.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1098 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
- This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the 'info bar' which surrounds new portlets is displayed by default.
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1098 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the 'info bar' which surrounds new portlets is displayed by default.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1099 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1099 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In this release, the Single Sign On (SSO) component has been enhanced to support FORM authentication for instances where the user can not get access to SSO authentication sessions (such as a Kerberos ticket). Users can now authenticate manually with the portal-specific username and password as a fall-back.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1116 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116</ulink>
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1116 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Configuring a page is no longer restricted to local portlets. It is now possible to define remote portlets (WSRP) in page descriptors to populate the base data for the page.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1140 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1140 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In previous releases, the portal did not indicate it had started clearly in the logs. Changes to core portal code now specifies the portal has started in the logs, and includes the portal version number for reference.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1149 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1149 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
This release contains enhancements to Gadgets, which, like portlets, can now be integrated on a page definition through XML descriptors.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1158 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1158 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The HTML Document Object Module (DOM) has been optimized to achieve better performance when transmitting markup, and has been simplified for faster rendering on recent web browsers. Older browsers such as Internet Explorer will still work, however performance will be degraded.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1169 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1169 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The Apache Shindig configuration file has been made more accessible to be modified more easily. It is now part of eXoGadgetServer.war/containers/default/container.js
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1197 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1197 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
An enhancement to the UserDashboardImpl object now allows dashboard instances to be reused. Dashboards now require less resources to operate correctly.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1210 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1210 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Cluster data transportation has been optimized to reduce the number of network connections and threads.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1250 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
- When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to "conserve", "insert", "merge" or "rewrite" the content previously imported.
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1250 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to "conserve", "insert", "merge" or "rewrite" the content previously imported.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1332 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1332 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In this release the default JCR workspace name and system JCR workspace name can now be configured in the configuration.properties file.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1349 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1349 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
There was no way to determine the Enterprise Portal Platform version, based on what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has been implemented, which allows the user to see what portal version is used by mouse-hovering in the site footer.
</para>
- </listitem>
- </varlistentry>
+
+ </listitem>
+ </varlistentry>
+
</variablelist>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-08 04:49:17 UTC (rev 8210)
@@ -1,35 +1,4 @@
-<?xml version='1.0'?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<variablelist>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1352 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1352">JBEPP-1352</ulink></term>
- <listitem>
-
- <remark>Assignee is: hfnukal</remark>
-
-
- <remark>JIRA is Closed</remark>
-
-
- <warning>
- <title>Not Public Yet - RHT only</title>
- <para>
- It was found that JBoss Web Services Native did not properly protect
-against recursive entity resolution when processing Document Type
-Definitions (DTD). A remote attacker could exploit this flaw by sending a
-specially-crafted HTTP POST request to a deployed web service, causing
-excessive CPU and memory consumption on the system hosting that service. If
-the attack is repeated to consume all available network sockets, the server
-will become unavailable. (CVE-2011-1483)
- </para>
- </warning>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
+<para>
+There are no known issues in this release.
+</para>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-08 04:49:17 UTC (rev 8210)
@@ -1,432 +1,626 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version='1.0'?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
+
+
<variablelist>
-<!-- https://issues.jboss.org/browse/JBEPP-348 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release.
+
+ <!-- https://issues.jboss.org/browse/JBEPP-348 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-353 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-353 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-631 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-631 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Remote Gadgets were not persisting data in category gadgets with more than five categories when the user switched between pages. User data entered in one screen was being lost when the user switched between pages. The fix implements changes to UIForm.js and UIFormCheckBoxInput.java which handles selected values reliably when the user switches between screens.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-699 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699</ulink>
- </term>
- <listitem>
- <remark>This issue is unassigned!</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-699 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699</ulink></term>
+ <listitem>
+
+ <remark>This issue is unassigned!</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A bug in UIUserLanguageSelector caused a problem with dynamically updating the locale when a user selected a different language. The language state had to be saved using the Apply button. The fix introduces changes to locale handling in the affected module which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-715 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715</ulink>
- </term>
- <listitem>
- <remark>This issue is unassigned!</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-715 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715</ulink></term>
+ <listitem>
+
+ <remark>This issue is unassigned!</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The page URL conventions in previous versions of JBoss Enterprise Portal Platform did not allow for Portal pages to have the same name. In these instances, pages with identical names were allocated the same URL, with only one page available through it. A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-763 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-763 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The platform ships with a resource compressor (CSS and Javascript). Some javascript files were incorrectly compressed and would break unless the developer mode was enabled. Enabling the developer mode introduced performance side-effects. The Javascript compression engine has been replaced, and can be turned off if required, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-900 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-900 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A bug in the Logo Portlet caused the processAction methods to be called once when the first, valid, processAction method was called to submit the value, and again when the page was rendered. This caused null values to be passed on the second submit. A fix to UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-901 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901</ulink>
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- When a "root" user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records.
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-901 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ When a "root" user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-903 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903</ulink>
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-903 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
An issue was identified when the OrganizationManagementPortlet displayed many users from the IDM DB. This caused performance issues, specifically impacting load times for the portlet. The fix implements performance optimizations for specific database queries related to the process. Load time performance is improved for the portlet.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-908 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908</ulink>
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-908 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
A performance issue in a database query that checked for duplicate emails at user registration caused unacceptable wait times. The larger the user count was in the database, the more pronounced the issue. The fix implements performance optimization in the database query. User registration wait time is improved for portal instances with very large user databases.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-927 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-927 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
It is not possible to save notes in the TODO gadget when the gadget is placed anywhere except a dashboard. This behavior is expected. A workaround to this issue has been implemented in this version, which allows notes to be entered into this gadget only. Other gadgets still have this issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-950 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-950 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
An inefficiency in MOPSessionManager cache was causing unacceptable wait times when an user accessed the portal for the first time, when the portal was idle for an extended period, or when accessing pages that had not been previously cached. The fix implements performance improvements for cases where a portal instance has many pages and navigation nodes, improving overall response time.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-951 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-951 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
Performance issues were discovered in the portal when editing a navigation, or portal page that contained many sub-pages. In some cases, the save action was taking longer than one minute to complete. The fix implements changes to the queries used to retrieve navigation, or portal pages after saving, which improves load times significantly.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-983 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983</ulink>
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
- An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-983 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-985 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-985 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
DateTimeValidator.java had an unnecessary check where the date input value needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1032 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032</ulink>
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1032 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A bug was discovered where a transaction commit related to IDM database operations was not placed within a final() block. Any misconfiguration, or operation failure, could cause the database connection to remain open. The fix ensures the transaction commit related to IDM database operations is placed within a final() block, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1048 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page > Container Title field. The vulnerability is fixed in this release.
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1048 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page > Container Title field. The vulnerability is fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1049 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1049 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1050 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1050 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1067 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067</ulink>
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1067 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
Only users from the LDAP database were shown in organization management if LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink IDM.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1082 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1082 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
If gadget restrict access to specific group, it was accessible for not members in Dashboard and page editing.
Now users cannot add restricted gadget.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1148 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1148 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set to FINE, which resulted in verbose log information. The fix removes the embedded logger configuration, which results in the JBoss Enterprise Application Platform server log configuration being used for logging.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1150 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mputz</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1150 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mputz</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1167 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1167 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A problem with regard to the location of token keys prevented Gadgets from working in load-balanced clustered portal environments. Token keys have been moved to a location accessible by all load-balanced clustered portal instances. Gadgets can now be used as intended.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1196 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
- A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as "text/rtf". The value should have been extracted as "application/rtf", which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type "application/rtf".
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1196 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as "text/rtf". The value should have been extracted as "application/rtf", which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type "application/rtf".
+
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1221 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1221 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A problem with the GroupManagement.java isAdministrator method caused a NullPointerException when the Organization Portlet is placed on a page and an anonymous user tries to access it. The fix changes the behavior of isAdministrator for anonymous users, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1241 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release.
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1241 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1243 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1243 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink>
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1293 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293</ulink>
- </term>
- <listitem>
- <remark>Assignee is: kenfinni</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1293 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: kenfinni</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not correctly handle exceptions. Exceptions that typically occurred during during afterPhase() were truncated (for example StaleObjectStateException in Hibernate commit). The Seam exception handler was not notified of the truncated exceptions therefore the application moves to a next page instead of an error page. The fix ensures org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener). Because exceptions are handled correctly, the Seam exception handler displays and error page given the appropriate conditions.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1310 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
- If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a function". The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page.
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1310 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a function". The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1319 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319</ulink>
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1319 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &lt;value-param&gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1324 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1324 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
It was found that the invoker servlets, deployed by default via
httpha-invoker, only performed access control on the HTTP GET and POST
methods, allowing remote attackers to make unauthenticated requests by
@@ -435,70 +629,102 @@
default installations unless an administrator has misconfigured the
security interceptor or disabled it. (CVE-2011-4085)
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1331 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
- When a portal host name contained the word "portal" in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word "portal" in the host name.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1331 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ When a portal host name contained the word "portal" in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word "portal" in the host name.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1336 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336</ulink>
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1336 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
It was found that the GateIn Portal contained verb-specific security constraints. As a result, authentication and authorization were only correctly applied to requests made using the GET and POST HTTP verbs. The GateIn Portal application does not allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue did not expose an exploitable security flaw. As a defence-in-depth measure, the verb-specific security constraints have been removed. Authentication and authorization now correctly apply to requests made using all HTTP verbs.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1351 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351</ulink>
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
- The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1351 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1357 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357</ulink>
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1357 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The Web Services for Remote Portlet (WSRP) configuration files for consumers and producer were previously only looked for in the WSRP extension archive. This resulted in extra configuration complexity for customers who wanted to edit the configuration directives for WSRP consumers and producer. The fix implements changes to the WSRP integration point that will now also look for WSRP configuration files in the conf/gatein directory of the active JBoss AS profile.
</para>
- </listitem>
- </varlistentry>
-<!-- https://issues.jboss.org/browse/JBEPP-1361 --> <varlistentry>
- <term>
- <ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361</ulink>
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1361 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361</ulink></term>
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all clustered nodes using the same password. The login process in Enterprise Portal Platform differed from normal authentication methods, and customers had to bypass standard authentication by enabling BASIC authentication, or patch login.jsp as described in the Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the patching and workarounds customers had to implement in earlier versions of the product, and increases overall platform security.
</para>
- </listitem>
- </varlistentry>
+
+ </listitem>
+ </varlistentry>
+
</variablelist>
Modified: epp/docs/branches/5.2/Release_Notes/publican.cfg
===================================================================
--- epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-08 04:49:17 UTC (rev 8210)
@@ -7,4 +7,4 @@
show_remarks: 1
cvs_branch: DOCS-RHEL-6
cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
-cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_BETA_Release_Notes-5.2-web-__LANG__
+cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_Release_Notes-5.2-web-__LANG__
13 years
- 1
- 0