gatein SVN: r7047 - in epp/docs/branches/5.1/Reference_Guide/en-US/modules: Advanced/JCR and 2 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-11 01:53:52 -0400 (Thu, 11 Aug 2011)
New Revision: 7047
Modified:
epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml
Log:
Prep for 5.1.1 release.
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml 2011-08-11 05:12:13 UTC (rev 7046)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml 2011-08-11 05:53:52 UTC (rev 7047)
@@ -24,7 +24,7 @@
-->
<section>
- <title><remark>Using AS Managed Datasources</remark></title>
+ <title>Using AS Managed Datasources</title>
<important>
<title>Supported Datasources</title>
<para>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2011-08-11 05:12:13 UTC (rev 7046)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2011-08-11 05:53:52 UTC (rev 7047)
@@ -5,7 +5,7 @@
]>
<section id="sect-Reference_Guide-LDAP_Integration">
- <title><remark>LDAP Integration</remark></title>
+ <title>LDAP Integration</title>
<note>
<title>Notational Device</title>
<para>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-08-11 05:12:13 UTC (rev 7046)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-08-11 05:53:52 UTC (rev 7047)
@@ -61,7 +61,7 @@
</section>
<section>
- <title><remark>Enabling SSO using JBoss SSO Valve</remark></title>
+ <title>Enabling SSO using JBoss SSO Valve</title>
<!-- Source Metadata
URL: https://issues.jboss.org/browse/JBQA-4530
Author [w/email]: Marek Posolda (mposolda(a)redhat.com)
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml 2011-08-11 05:12:13 UTC (rev 7046)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml 2011-08-11 05:53:52 UTC (rev 7047)
@@ -6,7 +6,7 @@
<chapter id="chap-Reference_Guide-Authentication_and_Identity">
<title>Authentication and Identity</title>
<section id="sect-Reference_Guide-Authentication_and_Identity-Password_Encryption" >
- <title><remark>Password Encryption</remark></title>
+ <title>Password Encryption</title>
<!--The warning and first listitem below were relocated from sect-Reference_Guide-Authentication_Token_Configuration as security and plain-text password issues were being expanded on (from JBEPP-610)-->
<warning>
<title>Username and passwords stored in clear text</title>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-11 05:12:13 UTC (rev 7046)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-11 05:53:52 UTC (rev 7047)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Reference_Guide-Portal_Navigation_Configuration">
- <title><remark>Portal Navigation Configuration</remark></title>
+ <title>Portal Navigation Configuration</title>
<section id="sect-Reference_Guide-Portal_Navigation_Configuration-Overview">
<title>Overview</title>
<para>
@@ -28,19 +28,19 @@
</listitem>
</itemizedlist>
<para>
- These navigations are configured using the standard XML syntax in the file; "<filename>02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename>".
+ These navigations are configured using the standard XML syntax in the file; <filename>02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename>.
</para>
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/default144.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- This XML configuration defines where in the portal's <literal>WAR</literal> to look for configuration settings, and which portals, groups, and user specific views to include in portal/group/user navigation.
+ This XML configuration defines where in the portal's <literal>WAR</literal> to look for configuration settings, and which portals, groups, and user specific views to include in <emphasis>portal/group/user</emphasis> navigation.
</para>
<para>
The first time the portal is launched those files will be used to create an initial navigation. That information will then be stored in the JCR content repository and can be modified and managed from the portal UI.
</para>
- <remark>Added based on Gatein revision 6987:</remark>
+ <!--DOC NOTE: Added based on Gatein revision 6987-->
<para>
-Each portal, groups and users navigation is indicated by a configuration paragraph, for example:
+ Each portal, groups and users navigation is indicated by a configuration paragraph, for example:
</para>
<programlistingco>
<areaspec>
@@ -75,42 +75,42 @@
<calloutlist>
<callout arearefs="area-Reference_Guide.Portalconf.predifinedOwner">
<para>
- <emphasis>predefinedOwner</emphasis> define the navigation owner, portal will look for the configuration files in folder with this name, if there is no suitable folder, a default portal will be created with name is this value.
+ <parameter>predefinedOwner</parameter> defines the navigation owner, portal will look for the configuration files in folder with this name, if there is no suitable folder, a default portal will be created with name is this value.
</para>
</callout>
<callout arearefs="area-Reference_Guide.Portalconf.ownerType">
<para>
- <emphasis> ownerType</emphasis> define the type of portal navigation. It may be a portal, group or user
+ <parameter>ownerType</parameter> define the type of portal navigation. It may be a portal, group or user
</para>
</callout>
<callout arearefs="area-Reference_Guide.Portalconf.templateLocation">
<para>
- <emphasis> templateLocation</emphasis> the classpath where contains all portal configuration files
+ <parameter>templateLocation</parameter> the classpath where contains all portal configuration files
</para>
</callout>
<callout arearefs="area-Reference_Guide.Portalconf.importMode">
<para>
- <emphasis> importMode</emphasis> The mode for navigation import. There are 4 types of import mode:
+ <parameter>importMode</parameter> The mode for navigation import. There are 4 types of import mode:
</para>
<itemizedlist>
<listitem>
<para>
- <emphasis>conserve</emphasis>: Import data when it does not exist, otherwise do nothing.
+ <parameter>conserve</parameter>: Import data when it does not exist, otherwise do nothing.
</para>
</listitem>
<listitem>
<para>
- <emphasis>insert</emphasis>: Import data when it does not exist, otherwise performs a strategy that adds new data only.
+ <parameter>insert</parameter>: Import data when it does not exist, otherwise performs a strategy that adds new data only.
</para>
</listitem>
<listitem>
<para>
- <emphasis>merge</emphasis>: Import data when it does not exist, update data when it exists.
+ <parameter>merge</parameter>: Import data when it does not exist, update data when it exists.
</para>
</listitem>
<listitem>
<para>
- <emphasis>rewrite</emphasis>: Overwrite data whatsoever.
+ <parameter>rewrite</parameter>: Overwrite data whatsoever.
</para>
</listitem>
</itemizedlist>
@@ -118,13 +118,18 @@
</calloutlist>
<para>
-Base on these parameters, portal will look for the configuration files and create a relevant portal navigation, pages and data import strategy. The portal configuration files will be stored in folders with path look like <literal>{templateLocation}/{ownerType}/{predefinedOwner}</literal>, all navigations are defined in the <literal>navigation.xml</literal> file, pages are defined in pages.xml and portal configuration is defined in <literal>{ownerType}.xml</literal>.
-For example, with the above configuration, portal will look for all configuration files from <literal>war:/conf/portal/portal/classic path.</literal>
+ Based on these parameters, the portal will look for the configuration files and create a relevant portal navigation, pages and data import strategy.
</para>
+ <para>
+ The portal configuration files will be stored in folders with path look like <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename>, all navigations are defined in the <filename>navigation.xml</filename> file, pages are defined in <filename>pages.xml</filename> and portal configuration is defined in <filename>{ownerType}.xml</filename>.
+ </para>
+ <para>
+ For example, with the above configuration, portal will look for all configuration files from <filename>war:/conf/portal/portal/classic path.</filename>
+ </para>
</section>
<section id="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation">
- <title><remark>Portal Navigation</remark></title>
+ <title>Portal Navigation</title>
<!-- Updated based on Gatein revision 6987 -->
<para>
The portal navigation incorporates the pages that can be accessed even when a user is not logged in (assuming the applicable permissions allow public access). For example; several portal navigations could be used when a company has multiple trademarks, and websites are set up for each of them.
@@ -144,7 +149,7 @@
<para>
It is also possible to apply a nested container that can also contain portlets. Row, column or tab containers are then responsible for the layout of their child portlets.
</para>
- <remark>Updated based on Gatein revision 6987:</remark>
+ <!--Updated based on Gatein revision 6987-->
<para>
Each application references a portlet using the id <literal>portal#{portalName}:/{portletWarName}/{portletName}/{uniqueId}</literal>.
</para>
@@ -162,7 +167,7 @@
<para>
This file defines all the navigation nodes the portal will have. The syntax is simple and uses nested node tags. Each node references a page defined in <filename>pages.xml</filename> file.
</para>
- <remark>Updated based on Gatein revision 6987:</remark>
+ <!--Updated based on Gatein revision 6987-->
<para>
If the administrator wants to create node labels for each language, they will have to use <literal>xml:lang</literal> attribute in the label tag with value of <literal>xml:lang</literal> is the relevant locale.
</para>
@@ -179,7 +184,7 @@
For top nodes, the <emphasis role="bold">uri</emphasis> and the <emphasis role="bold">name</emphasis> of your navigation nodes must have the <emphasis>same</emphasis> value. For other nodes the <emphasis role="bold">uri</emphasis> is a relative path.
</para>
<para>
- For example; <emphasis><uri>contentmanagement/fileexplorer</uri></emphasis> where '<literal>contentmanagement</literal> ' is the name of the parent node and '<literal>fileexplorer</literal>' is the name of the node ( <emphasis><name>fileexplorer</name> </emphasis> ).
+ For example; <emphasis><uri>contentmanagement/fileexplorer</uri></emphasis> where '<literal>contentmanagement</literal> ' is the name of the parent node and '<literal>fileexplorer</literal>' is the name of the node (<emphasis><name>fileexplorer</name> </emphasis>).
</para>
</warning>
</listitem>
@@ -240,19 +245,20 @@
<section id="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation">
- <title><remark>User Navigation</remark></title>
+ <title>User Navigation</title>
<para>
User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard.
</para>
- <remark>This Paragraph:</remark>
+ <!-- DOC NOTE: Get an answer on the below!-->
+ <!--<remark>This Paragraph:</remark>-->
<para>
Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>".
</para>
- <remark>Became this paragraph in GateIn r6987</remark>
+ <!--<remark>Became this paragraph in GateIn r6987</remark>
<para>
Three files configure the user navigation (<filename>navigation.xml</filename>, <filename>pages.xml</filename> and <filename>portlet-preferences.xml</filename>). They are located in the <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename> directory with <literal>ownerType</literal> is <literal>user</literal> and <literal>predefinedOwner</literal> is username that want to create the navigation. For example, if administrator want to create navigation for user <literal>root</literal>, he has to locate the configuration files in <filename>portal.war/WEB-INF/conf/portal/user/root </filename>
</para>
- <remark>Which is appropriate for EPP 5.1.1?</remark>
+ <remark>Which is appropriate for EPP 5.1.1?</remark>-->
<para>
The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard.
</para>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml 2011-08-11 05:12:13 UTC (rev 7046)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml 2011-08-11 05:53:52 UTC (rev 7047)
@@ -1311,7 +1311,7 @@
</section>
<section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP">
- <title><remark>Removing WSRP</remark></title>
+ <title>Removing WSRP</title>
<para>
If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation.
</para>
13 years, 4 months
- 1
- 0
gatein SVN: r7046 - in epp/docs/branches/5.1/Installation_Guide: en-US and 1 other directory.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-11 01:12:13 -0400 (Thu, 11 Aug 2011)
New Revision: 7046
Modified:
epp/docs/branches/5.1/Installation_Guide/en-US/Book_Info.xml
epp/docs/branches/5.1/Installation_Guide/en-US/Revision_History.xml
epp/docs/branches/5.1/Installation_Guide/publican.cfg
Log:
Updated for 5.1.1 release.
Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/Installation_Guide/en-US/Book_Info.xml 2011-08-11 04:52:38 UTC (rev 7045)
+++ epp/docs/branches/5.1/Installation_Guide/en-US/Book_Info.xml 2011-08-11 05:12:13 UTC (rev 7046)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<edition>2</edition>
- <pubsnumber>5.1.3</pubsnumber>
+ <pubsnumber>5.1.4</pubsnumber>
<abstract>
<para>
This book provides information about obtaining, installing and running JBoss Enterprise Portal Platform. It forms part of the complete document suite along with the <emphasis role="bold">User Guide</emphasis> and <emphasis role="bold">Reference Guide</emphasis> available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." />.
Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/Installation_Guide/en-US/Revision_History.xml 2011-08-11 04:52:38 UTC (rev 7045)
+++ epp/docs/branches/5.1/Installation_Guide/en-US/Revision_History.xml 2011-08-11 05:12:13 UTC (rev 7046)
@@ -9,7 +9,7 @@
<simpara>
<revhistory>
<revision>
- <revnumber>2-5.1.3</revnumber>
+ <revnumber>2-5.1.4</revnumber>
<date>Fri Jul 15 2011</date>
<author>
<firstname>Scott</firstname>
@@ -22,20 +22,6 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
- <revnumber>2-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>-->
<revision>
<revnumber>1-5.2</revnumber>
<date>Wed June 22 2011</date>
@@ -51,7 +37,7 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
+ <!-- <revision>
<revnumber>1-5.1</revnumber>
<date>Tue Dec 21 2010</date>
<author>
@@ -106,7 +92,7 @@
<member>Numerous bug fixes.</member>
</simplelist>
</revdescription>
- </revision>-->
+ </revision>
<revision>
<revnumber>1-2.3</revnumber>
<date>Mon Nov 29 2010</date>
@@ -177,7 +163,7 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
+ <revision>
<revnumber>1-1.7</revnumber>
<date>Tue Oct 26 2010</date>
<author>
@@ -204,7 +190,7 @@
<member>Edit Product version number for publishing restructure.</member>
</simplelist>
</revdescription>
- </revision>-->
+ </revision>
<revision>
<revnumber>1-1.3</revnumber>
<date>Tue Apr 28 2010</date>
@@ -232,7 +218,7 @@
<member>Updates as described in JBEPP-288 for the version 5.0 release.</member>
</simplelist>
</revdescription>
- </revision>
+ </revision>-->
<revision>
<revnumber>1-1.1</revnumber>
Modified: epp/docs/branches/5.1/Installation_Guide/publican.cfg
===================================================================
--- epp/docs/branches/5.1/Installation_Guide/publican.cfg 2011-08-11 04:52:38 UTC (rev 7045)
+++ epp/docs/branches/5.1/Installation_Guide/publican.cfg 2011-08-11 05:12:13 UTC (rev 7046)
@@ -6,7 +6,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
13 years, 4 months
- 1
- 0
gatein SVN: r7045 - in epp/docs/branches/5.1/Reference_Guide: en-US and 4 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-11 00:52:38 -0400 (Thu, 11 Aug 2011)
New Revision: 7045
Modified:
epp/docs/branches/5.1/Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.1/Reference_Guide/en-US/Reference_Guide.xml
epp/docs/branches/5.1/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml
epp/docs/branches/5.1/Reference_Guide/publican.cfg
Log:
Checking in remarked sections before removing highlights for 5.1.1 push
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/Book_Info.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/Book_Info.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<edition>2</edition>
- <pubsnumber>5.1.2</pubsnumber>
+ <pubsnumber>5.1.7</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.1/Reference_Guide/en-US/Reference_Guide.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/Reference_Guide.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/Reference_Guide.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -3,15 +3,15 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent">
%BOOK_ENTITIES;
]>
-<book status="draft">
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<book>
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/PortalDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/PortletDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/PortalDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/PortletDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!--<xi:include href="modules/GadgetDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
- <xi:include href="modules/AuthenticationAndIdentity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/WSRP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Advanced.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/AuthenticationAndIdentity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/WSRP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Advanced.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</book>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/Revision_History.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/Revision_History.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -8,6 +8,76 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>2-5.1.7</revnumber>
+ <date>Thu Aug 11 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Prep for 5.1.1 release.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <!-- <revision>
+ <revnumber>2-5.1.6</revnumber>
+ <date>Wed Aug 10 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Incorporated QA feedback.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>2-5.1.5</revnumber>
+ <date>Fri Aug 5 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Incorporated changes from GateIn revision 6987.</member>
+ </simplelist>
+ </revdescription>
+ </revision> -->
+ <revision>
+ <revnumber>2-5.1.4</revnumber>
+ <date>Tue Aug 2 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>JBEPP-894: Updated 'Enable SSO' section.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <!--<revision>
+ <revnumber>2-5.1.3</revnumber>
+ <date>Mon Aug 1 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>JBEPP-894: Added Section 14.7.2. Enabling SSO.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>2-5.1.2</revnumber>
<date>Fri Jul 15 2011</date>
<author>
@@ -21,7 +91,7 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
+ <revision>
<revnumber>2-5.1.1</revnumber>
<date>Monday June 27 2011</date>
<author>
@@ -34,7 +104,7 @@
<member>Updated for 5.1.1 Release.</member>
</simplelist>
</revdescription>
- </revision>-->
+ </revision>
<revision>
<revnumber>1-5.8</revnumber>
<date>Wed June 22 2011</date>
@@ -78,7 +148,7 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
+ <revision>
<revnumber>1-5.5</revnumber>
<date>Thu May 12 2011</date>
<author>
@@ -217,7 +287,7 @@
<member>Republished for 5.1 branch.</member>
</simplelist>
</revdescription>
- </revision> -->
+ </revision>
<revision>
<revnumber>1-1.21</revnumber>
<date>Wed Dec 01 2010</date>
@@ -232,7 +302,7 @@
</simplelist>
</revdescription>
</revision>
- <!-- <revision>
+ <revision>
<revnumber>1-1.20</revnumber>
<date>Mon Nov 29 2010</date>
<author>
@@ -304,7 +374,7 @@
<member>Updated to remove numerous minor spelling and typographic errors.</member>
</simplelist>
</revdescription>
- </revision> -->
+ </revision>
<revision>
<revnumber>1-1.13</revnumber>
<date>Tue Oct 26 2010</date>
@@ -319,7 +389,7 @@
</simplelist>
</revdescription>
</revision>
-<!-- <revision>
+ <revision>
<revnumber>1-1.11</revnumber>
<date>Thu Sep 30 2010</date>
<author>
@@ -360,7 +430,7 @@
<member>Started content for "Debugging Resource Bundle Usage" section. Started homoginizing filepath variables.</member>
</simplelist>
</revdescription>
- </revision> -->
+ </revision>
<revision>
<revnumber>1-1.8</revnumber>
<date>Fri Aug 27 2010</date>
@@ -375,7 +445,7 @@
</simplelist>
</revdescription>
</revision>
-<!-- <revision>
+ <revision>
<revnumber>1-1.7</revnumber>
<date>Mon Aug 9 2010</date>
<author>
@@ -388,7 +458,7 @@
<member>Further clean-up of programlisting rendering.</member>
</simplelist>
</revdescription>
- </revision> -->
+ </revision>
<revision>
<revnumber>1-1.6</revnumber>
<date>Thu Aug 5 2010</date>
@@ -403,7 +473,7 @@
</simplelist>
</revdescription>
</revision>
-<!-- <revision>
+ <revision>
<revnumber>1-1.5</revnumber>
<date>Thu Jul 29 2010</date>
<author>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/Advanced/JCR/as_managed_datasources.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -9,7 +9,7 @@
The EAP Admin and Config Guide
URL: http://docs/docs/en-US/JBoss_Enterprise_Application_Platform/5/html-singl...
-Author: ECS
+Author: Misty Stanley-Jones (RH; ECS)
License: CC-BY-SA
The eXo Platoform Reference Guide
@@ -122,8 +122,7 @@
<term><depends></term>
<listitem>
<para>
- The <literal>ObjectName</literal> of an MBean service this <classname>ConnectionFactory</classname>
- or<classname>DataSource</classname> deployment depends upon. The connection manager service will not be started until the dependent services have been started.
+ The <literal>ObjectName</literal> of an MBean service this <classname>ConnectionFactory</classname> or <classname>DataSource</classname> deployment depends upon. The connection manager service will not be started until the dependent services have been started.
</para>
</listitem>
</varlistentry>
@@ -176,19 +175,19 @@
<itemizedlist>
<title>Possible values for <transaction-isolation></title>
<listitem>
- <para>TRANSACTION_READ_UNCOMMITTED</para>
+ <para><parameter>TRANSACTION_READ_UNCOMMITTED</parameter></para>
</listitem>
<listitem>
- <para>TRANSACTION_READ_COMMITTED</para>
+ <para><parameter>TRANSACTION_READ_COMMITTED</parameter></para>
</listitem>
<listitem>
- <para>TRANSACTION_REPEATABLE_READ</para>
+ <para><parameter>TRANSACTION_REPEATABLE_READ</parameter></para>
</listitem>
<listitem>
- <para>TRANSACTION_SERIALIZABLE</para>
+ <para><parameter>TRANSACTION_SERIALIZABLE</parameter></para>
</listitem>
<listitem>
- <para>TRANSACTION_NONE</para>
+ <para><parameter>TRANSACTION_NONE</parameter></para>
</listitem>
</itemizedlist>
</listitem>
@@ -229,7 +228,7 @@
<term><track-statements></term>
<listitem>
<para>
- Whether to monitor for unclosed Statements and ResultSets and issue warnings when they haven't been closed. The default value is <literal>NOWARN</literal>.
+ Whether to monitor for unclosed Statements and ResultSets and issue warnings when they have not been closed. The default value is <literal>NOWARN</literal>.
</para>
</listitem>
</varlistentry>
@@ -245,10 +244,10 @@
<term><share-prepared-statements></term>
<listitem>
<para>
- When the <prepared-statement-cache-size> is non-zero, determines whether two requests in the same transaction should return the same statement. Defaults to <literal>FALSE</literal>.
+ When the <parameter><prepared-statement-cache-size></parameter> is non-zero, determines whether two requests in the same transaction should return the same statement. Defaults to <literal>FALSE</literal>.
</para>
<example>
- <title>Using <share-prepared-statements></title>
+ <title>Using <parameter><share-prepared-statements></parameter></title>
<para>
The goal is to work around questionable driver behavior, where the driver applies auto-commit semantics to local transactions.
</para>
@@ -277,15 +276,15 @@
<term><query-timeout></term>
<listitem>
<para>
- The maximum time, in seconds, before a query times out. You can override this value by setting <set-tx-query-timeout> to <literal>TRUE</literal>.
+ The maximum time, in seconds, before a query times out. You can override this value by setting <parameter><set-tx-query-timeout></parameter> to <literal>TRUE</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><metadata>><type-mapping></term>
+ <term><type-mapping></term>
<listitem>
<para>
- A pointer to the type mapping in <filename>conf/standardjbosscmp.xml</filename>. A legacy from JBoss4.
+ A pointer to the type mapping in <filename>conf/standardjbosscmp.xml</filename>. This element is a child element of <parameter><metadata></parameter>. A legacy from JBoss4.
</para>
</listitem>
</varlistentry>
@@ -293,7 +292,7 @@
<term><validate-on-match></term>
<listitem>
<para>
- Whether to validate the connection when the JCA layer matches a managed connection, such as when the connection is checked out of the pool. With the addition of <background-validation> this is not required. It is usually not necessary to specify <literal>TRUE</literal> for <validate-on-match> in conjunction with specifying <literal>TRUE</literal> for <background-validation>. Defaults to <literal>TRUE</literal>.
+ Whether to validate the connection when the JCA layer matches a managed connection, such as when the connection is checked out of the pool. With the addition of <parameter><background-validation></parameter> this is not required. It is usually not necessary to specify <literal>TRUE</literal> for <parameter><validate-on-match></parameter> in conjunction with specifying <literal>TRUE</literal> for <parameter><background-validation></parameter>. Defaults to <literal>TRUE</literal>.
</para>
</listitem>
</varlistentry>
@@ -309,7 +308,7 @@
<term><background-validation></term>
<listitem>
<para>
- Background connection validation reduces the overall load on the RDBMS system when validating a connection. When using this feature, EAP checks whether the current connection in the pool a separate thread (ConnectionValidator). <background-validation-minutes> depends on this value also being set to <literal>TRUE</literal>. Defaults to <literal>FALSE</literal>.
+ Background connection validation reduces the overall load on the RDBMS system when validating a connection. When using this feature, EAP checks whether the current connection in the pool a separate thread (ConnectionValidator). <parameter><background-validation-minutes></parameter> depends on this value also being set to <literal>TRUE</literal>. Defaults to <literal>FALSE</literal>.
</para>
</listitem>
</varlistentry>
@@ -317,12 +316,10 @@
<term><background-validation-millis></term>
<listitem>
<para>
- Background connection validation reduces the overall load on the RDBMS system when validating a
- connection. Setting this parameter means that JBoss will attempt to validate the current connections in
- the pool as a separate thread (<classname>ConnectionValidator</classname>). This parameter's value
- defines the interval, in milliseconds, for which the <classname>ConnectionValidator</classname> will
- run. (This value should not be the same as your <literal><![CDATA[<idle-timeout-minutes]]></literal>
- value.)
+ Background connection validation reduces the overall load on the RDBMS system when validating a connection. Setting this parameter means that JBoss will attempt to validate the current connections in the pool as a separate thread (<classname>ConnectionValidator</classname>). This parameter's value defines the interval, in milliseconds, for which the <classname>ConnectionValidator</classname> will run.
+ </para>
+ <para>
+ This value should not be the same as your <literal><idle-timeout-minutes></literal> value.
</para>
</listitem>
@@ -362,7 +359,7 @@
</para>
<note>
<para>
- You should set this to a smallervalue than <idle-timeout-minutes>, unless you have specified <min-pool-size> a minimum pool size set.
+ You should set this to a smallervalue than <parameter><idle-timeout-minutes></parameter>, unless you have specified <parameter><min-pool-size></parameter> a minimum pool size set.
</para>
</note>
</listitem>
@@ -371,7 +368,7 @@
<term><url-delimiter>, <url-property>, <url-selector-strategy-class-name></term>
<listitem>
<para>
- Parameters dealing with database failover. As of JBoss Enterprise Application Platform 5.1, these are configured as part of the main datasource configuration. In previous versions, <url-delimiter> appeared as <url-delimeter>.
+ Parameters dealing with database failover. As of JBoss Enterprise Application Platform 5.1, these are configured as part of the main datasource configuration. In previous versions, <parameter><url-delimiter></parameter> appeared as <parameter><url-delimeter></parameter>.
</para>
</listitem>
</varlistentry>
@@ -395,7 +392,7 @@
<term><min-pool-size></term>
<listitem>
<para>
- The minimum number of connections maintained in the pool. Unless <prefill> is <literal>TRUE</literal>, the pool remains empty until the first use, at which point the pool is filled to the <min-pool-size>. When the pool size drops below the <min-pool-size> due to idle timeouts, the pool is refilled to the <min-pool-size>. Defaults to <literal>0</literal>.
+ The minimum number of connections maintained in the pool. Unless <parameter><prefill></parameter> is <literal>TRUE</literal>, the pool remains empty until the first use, at which point the pool is filled to the <parameter><min-pool-size></parameter>. When the pool size drops below the <parameter><min-pool-size></parameter> due to idle timeouts, the pool is refilled to the <parameter><min-pool-size></parameter>. Defaults to <literal>0</literal>.
</para>
</listitem>
</varlistentry>
@@ -444,7 +441,7 @@
Used to configure the connections retrieved from the <classname>java.sql.Driver</classname>.
</para>
<example>
- <title>Example <connection-property></title>
+ <title>Example <parameter><connection-property></parameter></title>
<programlisting language="XML" role="XML">
<connection-property name="char.encoding">UTF-8</connection-property>
</programlisting>
@@ -469,7 +466,7 @@
Properties used to configure the <classname>XADataSource</classname>.
</para>
<example>
- <title>Example <xa-datasource-property> Declarations</title>
+ <title>Example <parameter><xa-datasource-property> Declarations</parameter></title>
<programlisting language="XML" role="XML"><xa-datasource-property name="IfxWAITTIME">10</xa-datasource-property>
<xa-datasource-property name="IfxIFXHOST">myhost.mydomain.com</xa-datasource-property>
<xa-datasource-property name="PortNumber">1557</xa-datasource-property>
@@ -517,9 +514,7 @@
<variablelist>
<title>Security Parameters</title>
<varlistentry>
- <term>
- <literal><![CDATA[<application-managed-security>]]></literal>
- </term>
+ <term><application-managed-security></term>
<listitem>
<para>
Uses the username and password passed on the <methodname>getConnection</methodname> or
@@ -528,9 +523,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>
- <literal><![CDATA[<security-domain>]]></literal>
- </term>
+ <term><security-domain></term>
<listitem>
<para>
Uses the identified login module configured in <filename>conf/login-module.xml</filename>.
@@ -538,9 +531,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>
- <literal><![CDATA[<security-domain-and-application>]]></literal>
- </term>
+ <term><security-domain-and-application></term>
<listitem>
<para>
Uses the identified login module configured in <filename>conf/login-module.xml</filename> and other
@@ -590,7 +581,7 @@
</variablelist>
<para>
The fields in <xref linkend="xa-recovery-parameters" /> should have a fall back value of their non-recover
- counterparts: <user-name>,< password> and <security-domain>.
+ counterparts: <parameter><user-name></parameter>, <parameter>< password></parameter> and <parameter><security-domain></parameter>.
</para>
</section>
<section>
@@ -619,7 +610,7 @@
</para>
<note>
<para>
- Use of the <use-java-context> setting is not recommended in a production environment. It requires accessing a
+ Use of the <parameter><use-java-context></parameter> setting is not recommended in a production environment. It requires accessing a
connection pool remotely and this can cause unexpected problems, since connections are not serializable. Also,
transaction propagation is not supported, since it can lead to connection leaks if unreliability is present, such as
in a system crash or network failure. A remote session bean facade is the preferred way to access a datasource
@@ -632,7 +623,7 @@
<procedure>
<title>Configuring a Datasource to Use Login Modules</title>
<step>
- <title>Add the <security-domain-parameter> to the XML file for the datasource.</title>
+ <title>Add the <parameter><security-domain-parameter></parameter> to the XML file for the datasource.</title>
<programlisting language="XML" role="XML">
<datasources>
<local-tx-datasource>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -13,7 +13,7 @@
</para>
</note>
<para>
- <emphasis role="bold">LDAP</emphasis> (Lightweight Directory Access Protocol) is a set of open protocols used to access centrally stored information over a network. It is based on the X.500 standard for directory sharing, but is less complex and resource-intensive
+ <emphasis role="bold">LDAP</emphasis> (Lightweight Directory Access Protocol) is a set of open protocols used to access centrally stored information over a network. It is based on the X.500 standard for directory sharing, but is less complex and resource-intensive.
</para>
<para>
Using a client/server architecture, LDAP provides a reliable means to create a central information directory accessible from the network. When a client attempts to modify information within this directory, the server verifies the user has permission to make the change, and then adds or updates the entry as requested. To ensure the communication is secure, the Secure Sockets Layer (<emphasis>SSL</emphasis>) or Transport Layer Security (<emphasis>TLS</emphasis>) cryptographic protocols can be used to prevent an attacker from intercepting the transmission.
@@ -285,8 +285,10 @@
</step>
<step>
<para>
- Comment out the default Picketlink <literal>config</literal> value: <parameter>war:/conf/organization/picketlink-idm/picketlink-idm-config.xml</parameter>
+ Comment out the default Picketlink <literal>config</literal> value:
</para>
+<programlisting language="XML" role="XML"><![CDATA[<value>war:/conf/organization/picketlink-idm/picketlink-idm-config.xml</value>
+]]></programlisting>
</step>
<step>
<para>
@@ -325,7 +327,8 @@
<para>
Uncomment the <parameter>groupTypeMappings</parameter> under "<emphasis>Uncomment for ACME LDAP example</emphasis>":
</para>
-<programlisting language="XML" role="XML"><![CDATA[<entry>
+<programlisting language="XML" role="XML"><![CDATA[<!-- Uncomment for ACME LDAP example -->
+<entry>
<key><string>/acme/roles/*</string></key>
<value><string>acme_roles_type</string></value>
</entry>
@@ -359,7 +362,8 @@
<para>
Uncomment the <parameter>groupTypeMappings</parameter> under "<emphasis>Uncomment for MSAD ReadOnly LDAP example</emphasis>":
</para>
-<programlisting language="XML" role="XML"><![CDATA[<entry>
+<programlisting language="XML" role="XML"><![CDATA[<!-- Uncomment for MSAD ReadOnly LDAP example -->
+<entry>
<key><string>/acme/roles/*</string></key>
<value><string>msad_roles_type</string></value>
</entry>
@@ -394,7 +398,8 @@
<para>
Uncomment the <parameter>groupTypeMappings</parameter> under "<emphasis>Uncomment for ACME LDAP example</emphasis>":
</para>
-<programlisting language="XML" role="XML"><![CDATA[<entry>
+<programlisting language="XML" role="XML"><![CDATA[<!-- Uncomment for ACME LDAP example -->
+<entry>
<key><string>/acme/roles/*</string></key>
<value><string>acme_roles_type</string></value>
</entry>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -61,7 +61,7 @@
</section>
<section>
- <title><remark>Enabling SSO using JBoss SSO valve</remark></title>
+ <title><remark>Enabling SSO using JBoss SSO Valve</remark></title>
<!-- Source Metadata
URL: https://issues.jboss.org/browse/JBQA-4530
Author [w/email]: Marek Posolda (mposolda(a)redhat.com)
@@ -73,40 +73,22 @@
Author [w/email]: Marek Posolda (mposolda(a)redhat.com)
-->
<para>
+ The JBoss SSO valve is useful to authenticate a user on one JBoss Enterprise Portal Platform node in a cluster and have that authentication automatically carry across to other nodes in the cluster.
+ </para>
+ <para>
+ This authentication can also be used in any other web applications which may require authentication, <emphasis role="bold">provided that these applications use same roles as the main portal instance</emphasis>. Attempting to use an SSO authentication in an application that uses different roles may create authentication errors (<emphasis role="bold">403</emphasis> errors, for example).
+ </para>
+
+ <para>
+ More info about the JBoss SSO valve can be found at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/Ad..."></ulink>.
+ </para>
+ <para>
To successfully implement SSO integration, do the following:
</para>
<procedure>
<title>SSO Integration</title>
<step>
<para>
- Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and ensure the following lines are present and unaltered:
- </para>
-
-<programlisting language="XML" role="XML"><![CDATA[<security-constraint>
- <web-resource-collection>
- <web-resource-name>HtmlAdaptor</web-resource-name>
- <description>An example security config that only allows users with the
- role JBossAdmin to access the HTML JMX console web application
- </description>
- <url-pattern>/*</url-pattern>
- </web-resource-collection>
- <auth-constraint>
- <role-name>JBossAdmin</role-name>
- </auth-constraint>
-</security-constraint>
-
-<login-config>
- <auth-method>BASIC</auth-method>
- <realm-name>JBoss JMX Console</realm-name>
-</login-config>
-
-<security-role>
- <role-name>JBossAdmin</role-name>
-</security-role>
-]]></programlisting>
- </step>
- <step>
- <para>
Open the <filename>/<replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file and uncomment one of the two <parameter>Valve</parameter> entries:
</para>
<itemizedlist>
@@ -201,6 +183,187 @@
</itemizedlist>
</step>
</procedure>
+ <formalpara>
+ <title>Testing the SSO Valve</title>
+ <para>
+ Once the JBoss SSO Valve has been enabled, it can be tested with the following steps:
+ </para>
+ </formalpara>
+ <procedure>
+ <title>Testing the SSO Vavle</title>
+ <step>
+ <para>
+ Copy the <replaceable><PROFILE></replaceable> you enabled the valve in (<literal>default</literal>, for example) into two new profiles called <literal>node1</literal> and <literal>node2</literal>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Run an instance of JBoss Enterprise Portal Platform using the <literal>node1</literal> profile on a local machine:
+ </para>
+<programlisting>./run.sh -c node1 -Djboss.service.binding.set=ports-default -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 &
+</programlisting>
+ </step>
+ <step>
+ <para>
+ Start another instance using the <literal>node2</literal> profile:
+ </para>
+<programlisting>./run.sh -c node2 -Djboss.service.binding.set=ports-01 -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=1 &
+</programlisting>
+ </step>
+ <step>
+ <para>
+ Navigate to <ulink type="http" url="http://localhost:8080/portal/private/classic"></ulink> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn</systemitem>").
+ </para>
+ </step>
+ <step>
+ <para>
+ Navigate to <ulink type="http" url="http://localhost:8180/portal/private/classic"></ulink>. You should be automatically authenticated as user <systemitem>root</systemitem> on this node as well.
+ </para>
+ </step>
+ </procedure>
+ <formalpara>
+ <title>Enabling SSO in a physical cluster</title>
+ <para>
+ If you require SSO to work across a physical cluster of separate machines you will need to use the <parameter>cookieDomain</parameter> attribute of the SSO valve.
+ </para>
+ </formalpara>
+ <procedure>
+ <step>
+ <para>
+ Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file.
+ </para>
+ </step>
+ <step>
+ <para>
+ Uncomment the line:
+ </para>
+<programlisting language="XML" role="XML"><![CDATA[<!--
+<Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
+-->
+]]></programlisting>
+ </step>
+ <step>
+ <para>
+ And edit it to match the following:
+ </para>
+<programlisting language="XML" role="XML"><![CDATA[<Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" cookieDomain="yourdomain.com" />
+]]></programlisting>
+ <para>
+ (Where <literal>yourdomain.com</literal> is the domain used in your cluster. For example; <ulink type="http" url="http://machine1.yourdomain.com:8080/portal/private/classic"></ulink> and <ulink type="http" url="http://machine2.yourdomain.com:8080/portal/private/classic"></ulink>)
+ </para>
+ </step>
+ <step>
+ <para>
+ Repeat the process in the other nodes in the cluster.
+ </para>
+ </step>
+ </procedure>
+
+ <para>
+ This will ensure the <literal>JSESSIONIDSSO</literal> cookie is be used in the correct domain, allowing the SSO authentication to occur.
+ </para>
+ <formalpara>
+ <title>Enabling SSO with Other Web Applications</title>
+ <para>
+ As mentioned earlier, in order to use SSO authentication between JBoss Enterprise Portal Platform instances and other web applications, the roles defined in the web application must match those used in the portal instance.
+ </para>
+ </formalpara>
+ <para>
+ As an example, to use the SSO Valve to authenticate a user in both a portal instance and the JMX Console, the following actions would be required:
+ </para>
+ <procedure>
+ <title></title>
+ <step>
+ <para>
+ Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and edit it as follows:
+ </para>
+ <substeps>
+ <step>
+ <para>
+ Change the <parameter><role-name></parameter> entry in the <parameter><auth-constraint></parameter> element (line <literal>110</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal>:
+ </para>
+<programlisting language="XML" role="XML"><![CDATA[<auth-constraint>
+ <!--<role-name>JBossAdmin</role-name>-->
+ <role-name>users</role-name>
+</auth-constraint>]]></programlisting>
+ </step>
+ <step>
+ <para>
+ Change the <parameter><role-name></parameter> entry in the <parameter><security-role></parameter> element (line <literal>120</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal>
+ </para>
+<programlisting language="XML" role="XML"><![CDATA[<security-role>
+ <!--<role-name>JBossAdmin</role-name>-->
+ <role-name>users</role-name>
+</security-role>]]></programlisting>
+ </step>
+ </substeps>
+ </step>
+ </procedure>
+ <formalpara>
+ <title>Testing SSO With Other Web Applications</title>
+ <para>
+ To test that SSO authentication is enabled from portal instances to other web applications (in this case, the JMX Console), do the following:
+ </para>
+ </formalpara>
+ <procedure>
+ <title>Test SSO Between Portal and JMX Console</title>
+ <step>
+ <para>
+ Start a portal instance on one node:
+ </para>
+<programlisting>./run.sh -c node1 -Djboss.service.binding.set=ports-default -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 &
+</programlisting>
+ </step>
+ <step>
+ <para>
+ Navigate to <ulink type="http" url="http://localhost:8080/portal/private/classic"></ulink> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn</systemitem>").
+ </para>
+ </step>
+ <step>
+ <para>
+ Navigate to <ulink type="http" url="http://localhost:8080/jmx-console"></ulink>. You should be automatically authenticated into the JMX Console.
+ </para>
+ </step>
+ </procedure>
+ <formalpara>
+ <title>Using SSO to Authenticate From the Public Page</title>
+ <para>
+ The previous configuration changes in this section are useful if a user is using a private URL (<ulink type="http" url="http://localhost:8080/portal/private/classic"></ulink>, for example) to log in to the portal instance.
+ </para>
+ </formalpara>
+ <para>
+ Further changes are needed however, if SSO authentication is required to work with the <guilabel>Sign In</guilabel> button on the front page of the portal (<ulink type="http" url="http://localhost:8080/portal/public/classic"></ulink>).
+ </para>
+ <para>
+ To enable this functionality, the <guilabel>Sign In</guilabel> link must redirect to the <filename>login.jsp</filename> file edited earlier to call the JAAS authentication directly.
+ </para>
+ <procedure>
+ <title>Redirect to Use SSO Valve Authentication</title>
+ <step>
+ <para>
+ Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file and edit the line:
+ </para>
+<programlisting language="Java" role="java"><![CDATA[<a class="Login" onclick="$signInAction"><%=_ctx.appRes("UILoginForm.label.Signin")%></a>
+]]></programlisting>
+ <para>
+ To read:
+ </para>
+<programlisting language="Java" role="java"><![CDATA[<a class="Login" href="/portal/private/classic"><%=_ctx.appRes("UILoginForm.label.Signin")%></a>
+]]></programlisting>
+ </step>
+ <step>
+ <para>
+ Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file and change the line:
+ </para>
+<programlisting language="Java" role="java"><![CDATA[<a onclick="$signInAction"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a>
+]]></programlisting>
+ <para>
+ To read:
+ </para>
+<programlisting language="Java" role="java"><![CDATA[<a href="/portal/private/classic"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a>
+]]></programlisting>
+ </step>
+ </procedure>
</section>
<section id="sect-Reference_Guide-SSO_Single_Sign_On-CAS_Central_Authentication_Service">
@@ -357,14 +520,14 @@
<title>Redirect to CAS</title>
<step>
<para>
- Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows:
+ Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows:
</para>
<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default106.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</step>
<step>
<para>
- Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows:
+ Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows:
</para>
<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default107.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
@@ -523,7 +686,7 @@
<title>Setup the portal to redirect to JOSSO</title>
<step>
<para>
- In the <filename>gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file modify the 'Sign In' link as follows:
+ In the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file modify the 'Sign In' link as follows:
</para>
<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default112.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
@@ -823,7 +986,7 @@
<title>Setup the portal to redirect to OpenSSO</title>
<step>
<para>
- Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows:
+ Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows:
</para>
<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default119.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -56,7 +56,7 @@
Start (or restart) your JBoss Enterprise Portal Platform.
</para>
<para>
- Any passwords written to the JCR will now be encoded and not plain-text.
+ Any passwords written to the JCR will now be encoded and not plain text.
</para>
</step>
</procedure>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -4,170 +4,263 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-Reference_Guide-Portal_Navigation_Configuration">
- <title>Portal Navigation Configuration</title>
- <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Overview">
- <title>Overview</title>
- <para>
- There are three types of navigation available to portal users:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation" />
- </para>
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Group_Navigation" />
- </para>
- </listitem>
- <listitem>
- <para>
- <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation" />
- </para>
- </listitem>
- </itemizedlist>
- <para>
- These navigations are configured using XML syntax in the file; "<filename>02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename>".
- </para>
-
+ <title><remark>Portal Navigation Configuration</remark></title>
+ <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Overview">
+ <title>Overview</title>
+ <para>
+ There are three types of navigation available to portal users:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation" />
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Group_Navigation" />
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation" />
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ These navigations are configured using the standard XML syntax in the file; "<filename>02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename>".
+ </para>
+
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/default144.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- This XML configuration defines where in the portal's <literal>WAR</literal> to look for configuration settings, and which portals, groups, and user specific views to include in portal/group/user navigation.
- </para>
- <para>
- The first time the portal is launched those files will be used to create an initial navigation. That information will then be stored in the JCR content repository and can be modified and managed from the portal UI.
- </para>
- </section>
+ <para>
+ This XML configuration defines where in the portal's <literal>WAR</literal> to look for configuration settings, and which portals, groups, and user specific views to include in portal/group/user navigation.
+ </para>
+ <para>
+ The first time the portal is launched those files will be used to create an initial navigation. That information will then be stored in the JCR content repository and can be modified and managed from the portal UI.
+ </para>
+ <remark>Added based on Gatein revision 6987:</remark>
+ <para>
+Each portal, groups and users navigation is indicated by a configuration paragraph, for example:
+ </para>
+<programlistingco>
+ <areaspec>
+ <area coords="5" id="area-Reference_Guide.Portalconf.predifinedOwner" />
+ <area coords="10" id="area-Reference_Guide.Portalconf.ownerType" />
+ <area coords="13" id="area-Reference_Guide.Portalconf.templateLocation" />
+ <area coords="16" id="area-Reference_Guide.Portalconf.importMode" />
+ </areaspec>
+<programlisting language="XML" role="XML"><![CDATA[<object-param>
+ <name>portal.configuration</name>
+ <description>description</description>
+ <object type="org.exoplatform.portal.config.NewPortalConfig">
+ <field name="predefinedOwner">
+ <collection type="java.util.HashSet">
+ <value><string>classic</string></value>
+ </collection>
+ </field>
+ <field name="ownerType">
+ <string>portal</string>
+ </field>
+ <field name="templateLocation">
+ <string>war:/conf/portal/</string>
+ </field>
+ <field name="importMode">
+ <string>conserve</string>
+ </field>
+ </object>
+</object-param>]]>
+</programlisting>
+</programlistingco>
-
- <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation">
- <title>Portal Navigation</title>
- <para>
- The portal navigation incorporates the pages that can be accessed even when a user is not logged in (assuming the applicable permissions allow public access). For example; several portal navigations could be used when a company has multiple trademarks, and websites are set up for each of them.
- </para>
- <para>
- The <emphasis>Classic</emphasis> portal is configured by three XML files in the <filename>02portal.war:/WEB-INF/conf/portal/portal/classic</filename> directory:
- </para>
- <variablelist>
- <varlistentry>
- <term>portal.xml</term>
- <listitem>
- <para>
- This file describes the layout and portlets that will be shown on all pages. Usually the layout contains the banner, footer, menu and breadcrumbs portlets. JBoss Enterprise Portal Platform is extremely configurable as every view element (even the banner and footer) is a portlet.
- </para>
-
+<calloutlist>
+ <callout arearefs="area-Reference_Guide.Portalconf.predifinedOwner">
+ <para>
+ <emphasis>predefinedOwner</emphasis> define the navigation owner, portal will look for the configuration files in folder with this name, if there is no suitable folder, a default portal will be created with name is this value.
+ </para>
+ </callout>
+ <callout arearefs="area-Reference_Guide.Portalconf.ownerType">
+ <para>
+ <emphasis> ownerType</emphasis> define the type of portal navigation. It may be a portal, group or user
+ </para>
+ </callout>
+ <callout arearefs="area-Reference_Guide.Portalconf.templateLocation">
+ <para>
+ <emphasis> templateLocation</emphasis> the classpath where contains all portal configuration files
+ </para>
+ </callout>
+ <callout arearefs="area-Reference_Guide.Portalconf.importMode">
+ <para>
+ <emphasis> importMode</emphasis> The mode for navigation import. There are 4 types of import mode:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>conserve</emphasis>: Import data when it does not exist, otherwise do nothing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>insert</emphasis>: Import data when it does not exist, otherwise performs a strategy that adds new data only.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>merge</emphasis>: Import data when it does not exist, update data when it exists.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>rewrite</emphasis>: Overwrite data whatsoever.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </callout>
+</calloutlist>
+
+ <para>
+Base on these parameters, portal will look for the configuration files and create a relevant portal navigation, pages and data import strategy. The portal configuration files will be stored in folders with path look like <literal>{templateLocation}/{ownerType}/{predefinedOwner}</literal>, all navigations are defined in the <literal>navigation.xml</literal> file, pages are defined in pages.xml and portal configuration is defined in <literal>{ownerType}.xml</literal>.
+For example, with the above configuration, portal will look for all configuration files from <literal>war:/conf/portal/portal/classic path.</literal>
+ </para>
+ </section>
+
+ <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation">
+ <title><remark>Portal Navigation</remark></title>
+ <!-- Updated based on Gatein revision 6987 -->
+ <para>
+ The portal navigation incorporates the pages that can be accessed even when a user is not logged in (assuming the applicable permissions allow public access). For example; several portal navigations could be used when a company has multiple trademarks, and websites are set up for each of them.
+ </para>
+ <para>
+ The <emphasis>Classic</emphasis> portal is configured by three XML files in the <filename>02portal.war:/WEB-INF/conf/portal/portal/classic</filename> directory:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>portal.xml</term>
+ <listitem>
+ <para>
+ This file describes the layout and portlets that will be shown on all pages. Usually the layout contains the banner, footer, menu and breadcrumbs portlets. JBoss Enterprise Portal Platform is extremely configurable as every view element (even the banner and footer) is a portlet.
+ </para>
+
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/portal.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- It is also possible to apply a nested container that can also contain portlets. Row, column or tab containers are then responsible for the layout of their child portlets.
- </para>
- <para>
- Each application references a portlet using its application name (usually the name of the WAR file)
-and a portlet reference (the name of the portlet as defined in portlet.xml).
- </para>
- <para>
- Use the <literal>page-body</literal> tag to define where JBoss Enterprise Portal Platform should render the current page.
- </para>
- <para>
- The defined <emphasis>classic</emphasis> portal is accessible to "Everyone" (at <literal>/portal/public/classic</literal>) but only members of the group <literal>/platform/administrators</literal> can edit it.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>navigation.xml</term>
- <listitem>
- <para>
- This file defines all the navigation nodes the portal will have. The syntax is simple and uses nested node tags. Each node references a page defined in <filename>pages.xml</filename> file.
- </para>
- <para>
- When the <literal>#{...}</literal> syntax is used in a <literal><label></literal> element, the enclosed property name serves as a key that is automatically passed to internationalization mechanism which replaces the literal property name with a localized value taken from the associated properties file matching the current locale.
- </para>
- <!-- DOC NOTE: Replaced code navigation.xml with code from GateIn commit r3831 (as per instruction from theute) -->
+ <para>
+ It is also possible to apply a nested container that can also contain portlets. Row, column or tab containers are then responsible for the layout of their child portlets.
+ </para>
+ <remark>Updated based on Gatein revision 6987:</remark>
+ <para>
+ Each application references a portlet using the id <literal>portal#{portalName}:/{portletWarName}/{portletName}/{uniqueId}</literal>.
+ </para>
+ <para>
+ Use the <literal>page-body</literal> tag to define where JBoss Enterprise Portal Platform should render the current page.
+ </para>
+ <para>
+ The defined <emphasis>classic</emphasis> portal is accessible to "Everyone" (at <literal>/portal/public/classic</literal>) but only members of the group <literal>/platform/administrators</literal> can edit it.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>navigation.xml</term>
+ <listitem>
+ <para>
+ This file defines all the navigation nodes the portal will have. The syntax is simple and uses nested node tags. Each node references a page defined in <filename>pages.xml</filename> file.
+ </para>
+ <remark>Updated based on Gatein revision 6987:</remark>
+ <para>
+ If the administrator wants to create node labels for each language, they will have to use <literal>xml:lang</literal> attribute in the label tag with value of <literal>xml:lang</literal> is the relevant locale.
+ </para>
+ <para>
+ Otherwise, if they want the node label is localized by resource bundle files, the <literal>#{...}</literal> syntax will be used, the enclosed property name serves as a key that is automatically passed to internationalization mechanism which replaces the literal property name with a localized value taken from the associated properties file matching the current locale.
+ </para>
+ <!-- DOC NOTE: Replaced code navigation.xml with code from GateIn commit r3831 (as per instruction from theute) -->
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/navigation.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- This navigation tree can have multiple views inside portlets (such as the breadcrumbs portlet) that render the current view node, the site map or the menu portlets.
- </para>
- <warning>
- <para>
- For top nodes, the <emphasis role="bold">uri</emphasis> and the <emphasis role="bold">name</emphasis> of your navigation nodes must have the <emphasis>same</emphasis> value. For other nodes the <emphasis role="bold">uri</emphasis> is a relative path.
- </para>
- <para>
- For example; <emphasis><uri>contentmanagement/fileexplorer</uri></emphasis> where '<literal>contentmanagement</literal> ' is the name of the parent node and '<literal>fileexplorer</literal>' is the name of the node ( <emphasis><name>fileexplorer</name> </emphasis> ).
- </para>
- </warning>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Subnodes</term>
- <listitem>
- <para>
- Subnodes can also be created using the following XML structure
- </para>
- <programlistingco>
- <areaspec>
- <area coords="9 40" id="area-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation-subpage" />
- </areaspec>
-
+ <para>
+ This navigation tree can have multiple views inside portlets (such as the breadcrumbs portlet) that render the current view node, the site map or the menu portlets.
+ </para>
+ <warning>
+ <para>
+ For top nodes, the <emphasis role="bold">uri</emphasis> and the <emphasis role="bold">name</emphasis> of your navigation nodes must have the <emphasis>same</emphasis> value. For other nodes the <emphasis role="bold">uri</emphasis> is a relative path.
+ </para>
+ <para>
+ For example; <emphasis><uri>contentmanagement/fileexplorer</uri></emphasis> where '<literal>contentmanagement</literal> ' is the name of the parent node and '<literal>fileexplorer</literal>' is the name of the node ( <emphasis><name>fileexplorer</name> </emphasis> ).
+ </para>
+ </warning>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Subnodes</term>
+ <listitem>
+ <para>
+ Subnodes can also be created using the following XML structure
+ </para>
+ <programlistingco>
+ <areaspec>
+ <area coords="9 40" id="area-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation-subpage" />
+ </areaspec>
+
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/subpage.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <calloutlist>
- <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation-subpage">
- <para>
- This element defines the parent/child relationship between a page and a subnode.
- </para>
- </callout>
- </calloutlist>
- </programlistingco>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>pages.xml</term>
- <listitem>
- <para>
+ <calloutlist>
+ <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation-subpage">
+ <para>
+ This element defines the parent/child relationship between a page and a subnode.
+ </para>
+ </callout>
+ </calloutlist>
+ </programlistingco>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>pages.xml</term>
+ <listitem>
+ <para>
This configuration file structure is very similar to <filename>portal.xml</filename> and it can also contain container tags (some usage examples of container tags can be found in <filename>02portal.war/WEB-INF/conf/portal/portal/sharedlayout.xml</filename>).
</para>
<para>
Each application can decide whether to render the portlet border, the window state, the icons or portlet's mode.
- </para>
+ </para>
<!-- DOC NOTE: look into including some actual examples of 'container tags' from sharedlayout.xml in place here. -->
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/pages.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
-
- <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Group_Navigation">
- <title>Group Navigation</title>
- <para>
- Group navigations are dynamically added to the user navigation at login. This allows users to see the pages assigned to any groups they belong to in the menu.
- </para>
- <para>
- The group navigation menu is configured by two XML files (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). The syntax used in these files is the same as those covered in <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation" />.
- </para>
- <para>
- They are located in <filename>02portal.war/WEB-INF/conf/portal/group<replaceable>/group-name-path/</replaceable></filename> directory (For example; <filename>02portal.war/WEB-INF/conf/portal/group/platform/administrators/</filename>).
- </para>
- </section>
+
+ <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Group_Navigation">
+ <title>Group Navigation</title>
+ <para>
+ Group navigations are dynamically added to the user navigation at login. This allows users to see the pages assigned to any groups they belong to in the menu.
+ </para>
+ <para>
+ The group navigation menu is configured by two XML files (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). The syntax used in these files is the same as those covered in <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation" />.
+ </para>
+ <para>
+ They are located in <filename>02portal.war/WEB-INF/conf/portal/group<replaceable>/group-name-path/</replaceable></filename> directory (For example; <filename>02portal.war/WEB-INF/conf/portal/group/platform/administrators/</filename>).
+ </para>
+ </section>
-
- <section id="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation">
- <title>User Navigation</title>
- <para>
- User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard.
- </para>
- <para>
- Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>".
- </para>
- <para>
- The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard.
- </para>
- <para>
- The example below shows a dashboard with all of the default gadgets included, as well as an extra currency converter gadget sourced from <ulink type="http" url="http://www.google.com/ig/directory?synd=open">Google Gadgets</ulink>.
- </para>
-
+
+ <section id="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation">
+ <title><remark>User Navigation</remark></title>
+ <para>
+ User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard.
+ </para>
+ <remark>This Paragraph:</remark>
+ <para>
+ Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>".
+ </para>
+ <remark>Became this paragraph in GateIn r6987</remark>
+ <para>
+ Three files configure the user navigation (<filename>navigation.xml</filename>, <filename>pages.xml</filename> and <filename>portlet-preferences.xml</filename>). They are located in the <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename> directory with <literal>ownerType</literal> is <literal>user</literal> and <literal>predefinedOwner</literal> is username that want to create the navigation. For example, if administrator want to create navigation for user <literal>root</literal>, he has to locate the configuration files in <filename>portal.war/WEB-INF/conf/portal/user/root </filename>
+ </para>
+ <remark>Which is appropriate for EPP 5.1.1?</remark>
+ <para>
+ The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard.
+ </para>
+ <para>
+ The example below shows a dashboard with all of the default gadgets included, as well as an extra currency converter gadget sourced from <ulink type="http" url="http://www.google.com/ig/directory?synd=open">Google Gadgets</ulink>.
+ </para>
+
<programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/gadgets.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </section>
+ </section>
</chapter>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/WSRP.xml 2011-08-11 04:52:38 UTC (rev 7045)
@@ -1313,10 +1313,10 @@
<section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP">
<title><remark>Removing WSRP</remark></title>
<para>
- If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, your installation will not be adversely affected should you leave the WSRP files in place.
+ If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation.
</para>
<para>
- However, if you wish to completely remove WSRP from your JBoss Enterprise Portal Platform installation, follow this procedure:
+ However, if you wish to completely remove WSRP from your portal installation, follow this procedure:
</para>
<procedure>
<title></title>
@@ -1430,11 +1430,6 @@
Save and exit the file.
</para>
</step>
- <step>
- <para>
- Remove all the <emphasis role="bold">WSRP</emphasis> SHA1 entries in the <filename>MANIFEST.MF</filename> file. They are not required.
- </para>
- </step>
</substeps>
</step>
<step>
Modified: epp/docs/branches/5.1/Reference_Guide/publican.cfg
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/publican.cfg 2011-08-11 04:41:47 UTC (rev 7044)
+++ epp/docs/branches/5.1/Reference_Guide/publican.cfg 2011-08-11 04:52:38 UTC (rev 7045)
@@ -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-Reference_Guide-5.1-web-__LANG__
\ No newline at end of file
13 years, 4 months
- 1
- 0
gatein SVN: r7044 - in epp/docs/branches/5.1/User_Guide: en-US and 6 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-11 00:41:47 -0400 (Thu, 11 Aug 2011)
New Revision: 7044
Added:
epp/docs/branches/5.1/User_Guide/en-US/modules/Supported_Browsers.xml
epp/docs/branches/5.1/User_Guide/en-US/modules/terms/Portlet_container_concept.xml
Modified:
epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml
epp/docs/branches/5.1/User_Guide/en-US/User_Guide.xml
epp/docs/branches/5.1/User_Guide/en-US/modules/Terms.xml
epp/docs/branches/5.1/User_Guide/en-US/modules/account/Account_and_Password_Retrieval.xml
epp/docs/branches/5.1/User_Guide/en-US/modules/gadgetsAdmin/Manage_Portlets_and_Gadgets.xml
epp/docs/branches/5.1/User_Guide/en-US/modules/portal/Manage_Portals.xml
epp/docs/branches/5.1/User_Guide/en-US/modules/portletsUser/Dashboard_Portlet.xml
epp/docs/branches/5.1/User_Guide/publican.cfg
Log:
Added Supported Browsers,Portlet Container Concept sections. Prep for 5.1.1 release.
Modified: epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<edition>2</edition>
- <pubsnumber>5.1.2</pubsnumber>
+ <pubsnumber>5.1.6</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and
Modified: epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -7,7 +7,63 @@
<title>Revision History</title>
<simpara>
<revhistory>
+ <revision>
+ <revnumber>2-5.1.6</revnumber>
+ <date>Thu Aug 11 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Prep for 5.1.1 release.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>2-5.1.5</revnumber>
+ <date>Wed Aug 10 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Incorporated QA feedback.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>2-5.1.4</revnumber>
+ <date>Thu Aug 4 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>BZ#692170: Added Portlet Container Concept section.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
<revision>
+ <revnumber>2-5.1.3</revnumber>
+ <date>Mon Aug 1 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Added "Supported Browsers" chapter.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <!--<revision>
<revnumber>2-5.1.2</revnumber>
<date>Fri Jul 15 2011</date>
<author>
@@ -21,7 +77,7 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
+ <revision>
<revnumber>2-5.1.1</revnumber>
<date>Monday June 27 2011</date>
<author>
@@ -34,7 +90,7 @@
<member>Updated for 5.1.1 Release.</member>
</simplelist>
</revdescription>
- </revision>-->
+ </revision>
<revision>
<revnumber>1-5.4</revnumber>
<date>Wed June 22 2011</date>
@@ -50,7 +106,7 @@
</simplelist>
</revdescription>
</revision>
- <!--<revision>
+ <revision>
<revnumber>1-5.3</revnumber>
<date>Wed Jun 01 2011</date>
<author>
@@ -63,7 +119,7 @@
<member>Added highlighting to 5.2.3 section header for review.</member>
</simplelist>
</revdescription>
- </revision> -->
+ </revision>
<revision>
<revnumber>1-5.2</revnumber>
<date>Thu Apr 7 2011</date>
@@ -78,7 +134,7 @@
</simplelist>
</revdescription>
</revision>
- <!-- <revision>
+ <revision>
<revnumber>1-5.1</revnumber>
<date>Tue Dec 21 2010</date>
<author>
Modified: epp/docs/branches/5.1/User_Guide/en-US/User_Guide.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/User_Guide.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/User_Guide.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -4,17 +4,18 @@
%BOOK_ENTITIES;
]>
<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Terms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/PortletsUser.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Account.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Portal.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Language.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/GadgetsAdmin.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="modules/Further_Documentation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Supported_Browsers.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Terms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/PortletsUser.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Account.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Portal.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Language.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/GadgetsAdmin.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/Further_Documentation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <index />
</book>
Added: epp/docs/branches/5.1/User_Guide/en-US/modules/Supported_Browsers.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/Supported_Browsers.xml (rev 0)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/Supported_Browsers.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -0,0 +1,43 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../User_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Supported Browsers</title>
+ <para>
+ JBoss Enterprise Portal Platform has been tested, and is supported, on the following web browsers:
+ </para>
+<!-- Source Metadata
+URL: https://jira.exoplatform.org/browse/WCM-1371
+Author [w/email]: Benjamin Paillereau (benjamin.paillereau(a)exoplatform.com)
+License:
+-->
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink type="http" url="http://www.mozilla.com/en-US/firefox/new/">Firefox</ulink> (versions 3 to 5).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink type="http" url="http://windows.microsoft.com/en-AU/internet-explorer/downloads/ie">Internet Explorer</ulink> (versions 7 and 8).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink type="http" url="http://www.google.com/chrome/">Google Chrome</ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink type="http" url="http://www.apple.com/safari/">Safari</ulink> (read-only).
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ This list will be expanded as newer browser versions are released and tested.
+ </para>
+</chapter>
\ No newline at end of file
Modified: epp/docs/branches/5.1/User_Guide/en-US/modules/Terms.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/Terms.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/Terms.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -4,13 +4,14 @@
%BOOK_ENTITIES;
]>
<chapter id="chap-User_Guide-Terms">
- <title>Glossary</title>
- <xi:include href="terms/Portal_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="terms/Portlet_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="terms/Toolbar_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="terms/Navigation_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="terms/Gadget_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="terms/Public_mode_and_Private_mode.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="terms/Permission_levels.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <title>Glossary</title>
+ <xi:include href="terms/Portal_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Portlet_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Portlet_container_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Toolbar_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Navigation_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Gadget_concept.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Public_mode_and_Private_mode.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="terms/Permission_levels.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</chapter>
Modified: epp/docs/branches/5.1/User_Guide/en-US/modules/account/Account_and_Password_Retrieval.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/account/Account_and_Password_Retrieval.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/account/Account_and_Password_Retrieval.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -4,111 +4,110 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Account_and_Password_Retrieval">
- <title>Account and Password Retrieval</title>
- <para>
- You can recover your username or password should you forget them by following these steps:
- </para>
- <procedure>
- <step>
- <para>
- Click the link '<emphasis role="bold">Forgot your User Name/Password?</emphasis>'
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/SignIn1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/SignIn1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
- </imageobject>
- </mediaobject>
- </step>
+ <title>Account and Password Retrieval</title>
+ <para>
+ You can recover your username or password should you forget them by following these steps:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Click the link '<emphasis role="bold">Forgot your User Name/Password?</emphasis>'
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/SignIn1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/SignIn1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
- <step>
- <para>
- The next screen offers two options:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Forgot my password</emphasis>.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">Forgot my username</emphasis>.
- </para>
- </listitem>
- </itemizedlist>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Forgot1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Forgot1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
- </imageobject>
- </mediaobject>
- <para>
- Select the appropriate option and click <emphasis role="bold">Next</emphasis>.
- </para>
- </step>
- <step>
- <para>
- You will be prompted to provide identification information depending on which option you selected:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- If you selected the <emphasis role="bold">Forgot my password</emphasis> option you will be prompted for your username:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/ForgotUserName1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/ForgotUserName1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm"/>
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- If you selected <emphasis role="bold">Forgot my username</emphasis> you will be prompted for your email address.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/ForgotEmail1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/ForgotEmail1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
- </imageobject>
- </mediaobject>
- </listitem>
- </itemizedlist>
- </step>
- </procedure>
- <para>
- After you submit the form an email will be send to your email address to assist you.
- </para>
- <para>
- If you forgot your password you will be sent a link to application that will allow you to edit your password. Your original password will not be valid after this email is sent.
- </para>
- <important>
- <title>Email Error</title>
- <para>
- If you receive an error message advising that the email could not be sent, you may need to configure (or reconfigure) your email settings in the <filename>configuration.properties</filename> file.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/EmailError.png" format="PNG" align="center" scale="90" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/EmailError.png" format="PNG" align="center" contentwidth="120mm" />
- </imageobject>
- <caption>Incorrect email settings error message</caption>
- </mediaobject>
- <para>
- More information about this configuration can be found in <emphasis role="bold">Section 5.2.2</emphasis> of the <emphasis role="bold">JBoss Enterprise Portal Platform Installation Guide</emphasis> at <ulink type="http" url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/">www.redhat.com</ulink>.
- </para>
- </important>
+ <step>
+ <para>
+ The next screen offers two options:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">Forgot my password</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Forgot my username</emphasis>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Forgot1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Forgot1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
+ </imageobject>
+ </mediaobject>
+ <para>
+ Select the appropriate option and click <emphasis role="bold">Next</emphasis>.
+ </para>
+ </step>
+ <step>
+ <para>
+ You will be prompted to provide identification information depending on which option you selected:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If you selected the <emphasis role="bold">Forgot my password</emphasis> option you will be prompted for your username:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/ForgotUserName1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/ForgotUserName1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ <listitem>
+ <para>
+ If you selected <emphasis role="bold">Forgot my username</emphasis> you will be prompted for your email address.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/ForgotEmail1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/ForgotEmail1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ </itemizedlist>
+ </step>
+ </procedure>
+ <para>
+ After you submit the form an email will be send to your email address to assist you.
+ </para>
+ <para>
+ If you forgot your password you will be sent a link to application that will allow you to edit your password. Your original password will not be valid after this email is sent.
+ </para>
+ <important>
+ <title>Email Error</title>
+ <para>
+ If you receive an error message advising that the email could not be sent, you may need to configure (or reconfigure) your email settings in the <filename>configuration.properties</filename> file.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/EmailError.png" format="PNG" align="center" scale="90" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/EmailError.png" format="PNG" align="center" contentwidth="120mm" />
+ </imageobject>
+ </mediaobject>
+ <para>
+ More information about this configuration can be found in <emphasis role="bold">Section 5.2.2</emphasis> of the <emphasis role="bold">JBoss Enterprise Portal Platform Installation Guide</emphasis> at <ulink type="http" url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/">www.redhat.com</ulink>.
+ </para>
+ </important>
</section>
Modified: epp/docs/branches/5.1/User_Guide/en-US/modules/gadgetsAdmin/Manage_Portlets_and_Gadgets.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/gadgetsAdmin/Manage_Portlets_and_Gadgets.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/gadgetsAdmin/Manage_Portlets_and_Gadgets.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -4,482 +4,490 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Manage_Portlets_and_Gadgets">
- <title>Manage Portlets and Gadgets</title>
- <para>
- Portlets and gadgets are organized in different categories. Each category contains one or several portlets or gadgets. You can also mix portlets and gadgets into one category. By default all gadgets are placed in the <emphasis>Gadgets</emphasis> category.
- </para>
-
- <section id="sect-User_Guide-Dashboard_Portlet-Display_Gadgets">
- <title>Display Gadgets</title>
- <para>
- You can change the number of columns available in the Dashboard.
- </para>
- <procedure>
- <step>
- <para>
- Go to the Dashboard (by clicking <emphasis role="bold">Dashboard</emphasis> in the Toolbar)
- </para>
- </step>
- <step>
- <para>
- Hover over <emphasis role="bold">Dashboard Editor</emphasis> and click <emphasis role="bold">Edit Page</emphasis> in the drop-down menu.
- </para>
- </step>
- <step>
- <para>
- The Page editor will appear.
- </para>
- </step>
- <step>
- <para>
- Hover over the <emphasis role="bold">Dashboard Portlet</emphasis> and click on the <emphasis role="bold">Edit</emphasis> icon (the 'pencil').
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Column.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Column.png" format="PNG" align="center" scalefit="1" contentwidth="120mm" />
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- Change the number of columns in the <emphasis role="bold">Number of columns</emphasis> field. The maximum number of columns is four (4).
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Dash_Column.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Dash_Column.png" format="PNG" align="center" contentwidth="130mm" />
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Save</emphasis> button to accept the change.
- </para>
- </step>
+ <title>Manage Portlets and Gadgets</title>
+ <para>
+ Portlets and gadgets are organized in different categories. Each category contains one or several portlets or gadgets. You can also mix portlets and gadgets into one category. By default all gadgets are placed in the <emphasis>Gadgets</emphasis> category.
+ </para>
+ <important>
+ <title>Gadget Preference Persistence</title>
+ <para>
+ Administrators and users should be aware that adding a gadget to any portal page other than the dashboard, will result in any user set preferences or modifications (adding entries to the TODO gadget, for example) <emphasis role="bold">not</emphasis> being saved in a persistent manner.
+ </para>
+ <para>
+ This limitation will be corrected in a later version of JBoss Enterprise Portal Platform.
+ </para>
+ </important>
+ <section id="sect-User_Guide-Dashboard_Portlet-Display_Gadgets">
+ <title>Display Gadgets</title>
+ <para>
+ You can change the number of columns available in the Dashboard.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Go to the Dashboard (by clicking <emphasis role="bold">Dashboard</emphasis> in the Toolbar)
+ </para>
+ </step>
+ <step>
+ <para>
+ Hover over <emphasis role="bold">Dashboard Editor</emphasis> and click <emphasis role="bold">Edit Page</emphasis> in the drop-down menu.
+ </para>
+ </step>
+ <step>
+ <para>
+ The Page editor will appear.
+ </para>
+ </step>
+ <step>
+ <para>
+ Hover over the <emphasis role="bold">Dashboard Portlet</emphasis> and click on the <emphasis role="bold">Edit</emphasis> icon (the 'pencil').
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Column.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Column.png" format="PNG" align="center" scalefit="1" contentwidth="120mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ Change the number of columns in the <emphasis role="bold">Number of columns</emphasis> field. The maximum number of columns is four (4).
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Dash_Column.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Dash_Column.png" format="PNG" align="center" contentwidth="130mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Save</emphasis> button to accept the change.
+ </para>
+ </step>
<step>
<para>
Click <emphasis role="bold">Close</emphasis> and then click <emphasis role="bold">Finish</emphasis>.
</para>
</step>
- </procedure>
+ </procedure>
- </section>
+ </section>
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_a_new_Category">
- <title>Add a new Category</title>
- <para>
- You easily add a new category by following this guide:
- </para>
- <procedure>
- <step>
- <para>
- Hover over the <emphasis role="bold">Group</emphasis> menu, then <emphasis role="bold">Administration</emphasis> and click on <emphasis role="bold">Application Registry</emphasis>.
- </para>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Add Category</emphasis> button on the action bar:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/AddCategory1.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/AddCategory1.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- <para>
- The <emphasis role="bold">Category Setting</emphasis> tab: includes common information about a category.
- </para>
-
- <variablelist>
- <varlistentry>
- <term>Category name</term>
- <listitem>
- <para>
- The name of the category. This field is required and its length must be between 3 and 30 characters. Only alpha, digit, dash and underscore characters are allowed.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Display name</term>
- <listitem>
- <para>
- The display name of the category and its length must be between 3 and 30 characters.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Description</term>
- <listitem>
- <para>
- A brief description of the category. Any length from 0 to 255 characters is allowed.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- The <emphasis role="bold">Permission Setting</emphasis> tab provides access to the Permission manager.
- </para>
- <para>The permission criteria are used whenever a user creates or modifies a page. In that case the user can only see and use portlets in those categories on which he or she has access to (as defined by groups and memberships).
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Permission2.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Permission2.png" format="PNG" align="center" scalefit="1" contentwidth="130mm" />
- </imageobject>
- </mediaobject>
- </step>
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_a_new_Category">
+ <title>Add a new Category</title>
+ <para>
+ You easily add a new category by following this guide:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Hover over the <emphasis role="bold">Group</emphasis> menu, then <emphasis role="bold">Administration</emphasis> and click on <emphasis role="bold">Application Registry</emphasis>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Add Category</emphasis> button on the action bar:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/AddCategory1.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/AddCategory1.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ <para>
+ The <emphasis role="bold">Category Setting</emphasis> tab: includes common information about a category.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Category name</term>
+ <listitem>
+ <para>
+ The name of the category. This field is required and its length must be between 3 and 30 characters. Only alpha, digit, dash and underscore characters are allowed.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Display name</term>
+ <listitem>
+ <para>
+ The display name of the category and its length must be between 3 and 30 characters.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Description</term>
+ <listitem>
+ <para>
+ A brief description of the category. Any length from 0 to 255 characters is allowed.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ The <emphasis role="bold">Permission Setting</emphasis> tab provides access to the Permission manager.
+ </para>
+ <para>The permission criteria are used whenever a user creates or modifies a page. In that case the user can only see and use portlets in those categories on which he or she has access to (as defined by groups and memberships).
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Permission2.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Permission2.png" format="PNG" align="center" scalefit="1" contentwidth="130mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
<!--
- <step>
- <para>
- Enter values for required fields in this form.
- </para>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Save</emphasis> button to accept adding a new category into a category list. The new category will be added into a list on the left pane.
- </para>
- </step>
+ <step>
+ <para>
+ Enter values for required fields in this form.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Save</emphasis> button to accept adding a new category into a category list. The new category will be added into a list on the left pane.
+ </para>
+ </step>
-->
- </procedure>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Edit_a_Category">
- <title>Edit a Category</title>
- <procedure>
- <step>
- <para>
- Click the Edit icon located next to the title bar.
- </para>
- </step>
- <step>
- <para>
- Update the category information.
- </para>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Save</emphasis> button to apply changes.
- </para>
- </step>
- </procedure>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Delete_a_Category">
- <title>Delete a Category</title>
- <procedure>
- <step>
- <para>
- Click the Trash can icon located next to the title bar.
- </para>
- </step>
- <step>
- <para>
- Accept the deletion by clicking <emphasis role="bold">OK</emphasis>
- </para>
- </step>
- </procedure>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_PortletsGadgets_to_the_specific_Category">
- <title>Add Applications to a Category</title>
- <procedure>
- <step>
- <para>
- Click the "Plus" icon located next to the category (in the list on the left) to which you want to add an application.
- </para>
- <para>
- The image below shows the available application. You will see this list when you click the "Plus" icon.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/AddPortlet2.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/AddPortlet2.png" format="PNG" align="center" scalefit="1" contentwidth="140mm" />
- </imageobject>
- </mediaobject>
- <variablelist>
- <varlistentry>
- <term>Display name</term>
- <listitem>
- <para>
- The display name of a portlet/gadget.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Application Type</term>
- <listitem>
- <para>
- Either Portlet, Gadget or WSRP application.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </step>
- <step>
- <para>
- Enter the display name and select a type
- </para>
- </step>
- <step>
- <para>
- Select an application by checking the radio button. Note that there several pages of Portlet applications to choose from and that the content of the list changes when you select a different type of application from the <emphasis role="bold">Application Type</emphasis> drop-down menu.
- </para>
- </step>
- <step>
- <para>
- Click the <emphasis role="bold">Save</emphasis> button to add the selected application to the category.
- </para>
- </step>
- </procedure>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Set_Access_Permission_on_Portlets">
- <title>Set Access Permission on Portlets</title>
+ </procedure>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Edit_a_Category">
+ <title>Edit a Category</title>
+ <procedure>
+ <step>
+ <para>
+ Click the Edit icon located next to the title bar.
+ </para>
+ </step>
+ <step>
+ <para>
+ Update the category information.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Save</emphasis> button to apply changes.
+ </para>
+ </step>
+ </procedure>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Delete_a_Category">
+ <title>Delete a Category</title>
+ <procedure>
+ <step>
+ <para>
+ Click the Trash can icon located next to the title bar.
+ </para>
+ </step>
+ <step>
+ <para>
+ Accept the deletion by clicking <emphasis role="bold">OK</emphasis>
+ </para>
+ </step>
+ </procedure>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_PortletsGadgets_to_the_specific_Category">
+ <title>Add Applications to a Category</title>
+ <procedure>
+ <step>
+ <para>
+ Click the "Plus" icon located next to the category (in the list on the left) to which you want to add an application.
+ </para>
+ <para>
+ The image below shows the available application. You will see this list when you click the "Plus" icon.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/AddPortlet2.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/AddPortlet2.png" format="PNG" align="center" scalefit="1" contentwidth="140mm" />
+ </imageobject>
+ </mediaobject>
+ <variablelist>
+ <varlistentry>
+ <term>Display name</term>
+ <listitem>
+ <para>
+ The display name of a portlet/gadget.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Application Type</term>
+ <listitem>
+ <para>
+ Either Portlet, Gadget or WSRP application.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </step>
+ <step>
+ <para>
+ Enter the display name and select a type
+ </para>
+ </step>
+ <step>
+ <para>
+ Select an application by checking the radio button. Note that there several pages of Portlet applications to choose from and that the content of the list changes when you select a different type of application from the <emphasis role="bold">Application Type</emphasis> drop-down menu.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the <emphasis role="bold">Save</emphasis> button to add the selected application to the category.
+ </para>
+ </step>
+ </procedure>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Set_Access_Permission_on_Portlets">
+ <title>Set Access Permission on Portlets</title>
- <procedure>
- <step>
- <para>
- In the <emphasis role="bold">Group</emphasis> menu, select <emphasis role="bold">Administration</emphasis> and then <emphasis role="bold">Application Registry</emphasis>.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/PortletPermission.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/PortletPermission.png" format="PNG" align="center" contentwidth="160mm"/>
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- Select a category in the Category pane that includes the portlet you want to set permissions on. All portlets of that category will be listed underneath.
- </para>
- </step>
- <step>
- <para>
- To set permission for a portlet:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Click the <emphasis role="bold">Add Permission</emphasis> button to add access permissions to more groups.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/AddPermission.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/AddPermission.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Or check <emphasis role="bold">Make it public</emphasis> to allow everyone to access.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- Whenever the user creates or modifies a page, he or she can only see and use gadgets/portlets that fulfill two conditions: the portlet is in a <emphasis role="bold">category</emphasis> which the user has access permission too and the user has access permission on the <emphasis role="bold">portlet</emphasis>
- </para>
- </step>
- </procedure>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-View_detail_information_of_the_specific_Portlets">
- <title>View/Edit portlet/gadget information</title>
- <para>
- In the <emphasis role="bold">Group</emphasis> menu, select <emphasis role="bold">Administration</emphasis> then <emphasis role="bold">Application Registry</emphasis>.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Org1.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Org1.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- <variablelist>
- <varlistentry>
- <term><emphasis role="bold">Left pane</emphasis></term>
- <listitem>
- <para>
- All portlets and gadgets grouped by categories
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Right pane</emphasis></term>
- <listitem>
- <para>
- shows detail information about a portlet: Name, Display name, Description and Portlet preferences.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- To see the details of any portlet select it from the list on the left.
- </para>
- <para>
- To edit a portlet, click the edit button to the right of the portlet's name:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/EditApplication.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/EditApplication.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/EditApplicationInformation.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/EditApplicationInformation.png" format="PNG" align="center" scalefit="1" contentwidth="90mm" />
- </imageobject>
- </mediaobject>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_a_Gadget">
- <title>Add a Gadget</title>
- <para>
- In the <emphasis role="bold">Group</emphasis> menu, select <emphasis role="bold">Administration</emphasis> then <emphasis role="bold">Application Registry</emphasis>. Click on the <emphasis role="bold">Gadget</emphasis> icon.
- </para>
- <para>
- You may add a remote gadget using its URL or create a brand-new one:
- </para>
+ <procedure>
+ <step>
+ <para>
+ In the <emphasis role="bold">Group</emphasis> menu, select <emphasis role="bold">Administration</emphasis> and then <emphasis role="bold">Application Registry</emphasis>.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/PortletPermission.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/PortletPermission.png" format="PNG" align="center" contentwidth="160mm"/>
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ Select a category in the Category pane that includes the portlet you want to set permissions on. All portlets of that category will be listed underneath.
+ </para>
+ </step>
+ <step>
+ <para>
+ To set permission for a portlet:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Click the <emphasis role="bold">Add Permission</emphasis> button to add access permissions to more groups.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/AddPermission.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/AddPermission.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ <listitem>
+ <para>
+ Or check <emphasis role="bold">Make it public</emphasis> to allow everyone to access.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Whenever the user creates or modifies a page, he or she can only see and use gadgets/portlets that fulfill two conditions: the portlet is in a <emphasis role="bold">category</emphasis> which the user has access permission too and the user has access permission on the <emphasis role="bold">portlet</emphasis>
+ </para>
+ </step>
+ </procedure>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-View_detail_information_of_the_specific_Portlets">
+ <title>View/Edit portlet/gadget information</title>
+ <para>
+ In the <emphasis role="bold">Group</emphasis> menu, select <emphasis role="bold">Administration</emphasis> then <emphasis role="bold">Application Registry</emphasis>.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Org1.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Org1.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ <variablelist>
+ <varlistentry>
+ <term><emphasis role="bold">Left pane</emphasis></term>
+ <listitem>
+ <para>
+ All portlets and gadgets grouped by categories
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Right pane</emphasis></term>
+ <listitem>
+ <para>
+ shows detail information about a portlet: Name, Display name, Description and Portlet preferences.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ To see the details of any portlet select it from the list on the left.
+ </para>
+ <para>
+ To edit a portlet, click the edit button to the right of the portlet's name:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/EditApplication.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/EditApplication.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/EditApplicationInformation.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/EditApplicationInformation.png" format="PNG" align="center" scalefit="1" contentwidth="90mm" />
+ </imageobject>
+ </mediaobject>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_a_Gadget">
+ <title>Add a Gadget</title>
+ <para>
+ In the <emphasis role="bold">Group</emphasis> menu, select <emphasis role="bold">Administration</emphasis> then <emphasis role="bold">Application Registry</emphasis>. Click on the <emphasis role="bold">Gadget</emphasis> icon.
+ </para>
+ <para>
+ You may add a remote gadget using its URL or create a brand-new one:
+ </para>
- <procedure>
- <title>Add a Remote Gadget</title>
- <step>
- <para>
- Click on <emphasis role="bold">Add a remote gadget</emphasis>:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/AddGadgetnew.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/AddGadgetnew.png" format="PNG" align="center" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- Enter the url of the remote gadget in the <emphasis role="bold">URL</emphasis> field.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/AddGadgetnewUrl.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/AddGadgetnewUrl.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- Click <emphasis role="bold">Add</emphasis>. The new remote gadget will be appear in gadget list on left pane.
- </para>
- </step>
- </procedure>
- <procedure>
- <title>Create a new Gadget</title>
- <step>
- <para>
- Click on <emphasis role="bold">Create a new gadget</emphasis>:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/CreateGadget1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/CreateGadget1.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- Populate the <literal>Source</literal> field with the xml code of the new gadget.
- </para>
- </step>
- </procedure>
- <para>
- You can edit or refresh a gadget using the icons in the top right of the <emphasis role="bold">Gadget Details</emphasis> pane.
- </para>
- <para>
- You can delete a local gadget using the trashcan icon to the right of the appropriate gadget in the gadget list.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/ActionGadget.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/ActionGadget.png" format="PNG" align="center" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_a_new_Gadget_to_the_Dashboard_Portlet">
- <title>Add a new Gadget to the Dashboard Portlet</title>
- <para>
- See <xref linkend="sect-User_Guide-Dashboard_Portlet-Add_Gadgets"/> for instructions on how to add new gadgets to the dashboard.
- </para>
- </section>
-
- <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Manage_Gadgets">
- <title>Manage Gadgets</title>
+ <procedure>
+ <title>Add a Remote Gadget</title>
+ <step>
+ <para>
+ Click on <emphasis role="bold">Add a remote gadget</emphasis>:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/AddGadgetnew.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/AddGadgetnew.png" format="PNG" align="center" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ Enter the url of the remote gadget in the <emphasis role="bold">URL</emphasis> field.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/AddGadgetnewUrl.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/AddGadgetnewUrl.png" format="PNG" align="center" scalefit="1" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ Click <emphasis role="bold">Add</emphasis>. The new remote gadget will be appear in gadget list on left pane.
+ </para>
+ </step>
+ </procedure>
+ <procedure>
+ <title>Create a new Gadget</title>
+ <step>
+ <para>
+ Click on <emphasis role="bold">Create a new gadget</emphasis>:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/CreateGadget1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/CreateGadget1.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ Populate the <literal>Source</literal> field with the xml code of the new gadget.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ You can edit or refresh a gadget using the icons in the top right of the <emphasis role="bold">Gadget Details</emphasis> pane.
+ </para>
+ <para>
+ You can delete a local gadget using the trashcan icon to the right of the appropriate gadget in the gadget list.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/ActionGadget.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/ActionGadget.png" format="PNG" align="center" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Add_a_new_Gadget_to_the_Dashboard_Portlet">
+ <title>Add a new Gadget to the Dashboard Portlet</title>
+ <para>
+ See <xref linkend="sect-User_Guide-Dashboard_Portlet-Add_Gadgets"/> for instructions on how to add new gadgets to the dashboard.
+ </para>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Portlets_and_Gadgets-Manage_Gadgets">
+ <title>Manage Gadgets</title>
- <section id="sect-User_Guide-Manage_Gadgets-Edit_a_Gadget">
- <title>Edit a Gadget</title>
- <para>
- Click the <emphasis role="bold">Edit Gadget</emphasis> icon located in the header of the <emphasis role="bold">Gadget Details</emphasis> page to display the following window:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Source.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Source.png" format="PNG" align="center" contentwidth="150mm" />
- </imageobject>
- </mediaobject>
- </section>
-
+ <section id="sect-User_Guide-Manage_Gadgets-Edit_a_Gadget">
+ <title>Edit a Gadget</title>
+ <para>
+ Click the <emphasis role="bold">Edit Gadget</emphasis> icon located in the header of the <emphasis role="bold">Gadget Details</emphasis> page to display the following window:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Source.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Source.png" format="PNG" align="center" contentwidth="150mm" />
+ </imageobject>
+ </mediaobject>
+ </section>
+
<!--Covered in section above SM
- <section id="sect-User_Guide-Manage_Gadgets-Refresh_a_Gadget">
- <title>Refresh a Gadget</title>
- <para>
- Click the <emphasis role="bold">Refresh information</emphasis> icon located in the header of the <emphasis role="bold">Gadget Details</emphasis> page to display the following window:
- </para>
+ <section id="sect-User_Guide-Manage_Gadgets-Refresh_a_Gadget">
+ <title>Refresh a Gadget</title>
+ <para>
+ Click the <emphasis role="bold">Refresh information</emphasis> icon located in the header of the <emphasis role="bold">Gadget Details</emphasis> page to display the following window:
+ </para>
- </section>
-
- <section id="sect-User_Guide-Manage_Gadgets-Delete_a_Gadget">
- <title>Delete a Gadget</title>
+ </section>
+
+ <section id="sect-User_Guide-Manage_Gadgets-Delete_a_Gadget">
+ <title>Delete a Gadget</title>
- <para>
- Click the trash can icon located next to the name of the gadget. An alert message should pop up asking for confirmation:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/Delete.png" format="PNG" align="center" />
- </imageobject>
- </mediaobject>
- </section> -->
+ <para>
+ Click the trash can icon located next to the name of the gadget. An alert message should pop up asking for confirmation:
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Delete.png" format="PNG" align="center" />
+ </imageobject>
+ </mediaobject>
+ </section> -->
- </section>
+ </section>
</section>
Modified: epp/docs/branches/5.1/User_Guide/en-US/modules/portal/Manage_Portals.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/portal/Manage_Portals.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/portal/Manage_Portals.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -161,7 +161,7 @@
</section>
<section id="proc-User_Guide-Manage_Portals-Edit_Layout">
- <title><remark>Edit Layout</remark></title>
+ <title>Edit Layout</title>
<para>
To edit the layout of a portal, click the <emphasis>Edit Layout</emphasis> key beside the active portal you wish to edit:
</para>
Modified: epp/docs/branches/5.1/User_Guide/en-US/modules/portletsUser/Dashboard_Portlet.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/portletsUser/Dashboard_Portlet.xml 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/portletsUser/Dashboard_Portlet.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -4,75 +4,75 @@
%BOOK_ENTITIES;
]>
<section id="sect-User_Guide-Dashboard_Portlet">
- <title>The Dashboard</title>
- <para>
- The Dashboard is used for hosting mini applications known as gadgets. The Dashboard uses a variety of graphical effects for displaying, opening and using gadgets.
- </para>
- <para>
- The active Dashboard can be individually named by double clicking on the default name ("<emphasis>Click and Type Page Name</emphasis>")...
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Dashname.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Dashname.png" format="PNG" align="center" scalefit="1" contentwidth="120mm"/>
- </imageobject>
- </mediaobject>
- <para>
- ...and entering a new name:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Dashname1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Dashname1.png" format="PNG" align="center" scalefit="1" contentwidth="120mm"/>
- </imageobject>
- </mediaobject>
- <para>
- The Dashboard can also be tabbed to create multiple spaces. Open a new tab by clicking the <emphasis role="bold">+</emphasis> button beside the Dashboard name.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/tabbed_dash.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/tabbed_dash.png" format="PNG" align="center" contentwidth="110mm" />
- </imageobject>
- </mediaobject>
- <para>
- New tabs can also be individually named and managed.
- </para>
- <para>
- Gadgets within the Dashboard can be moved and rearranged. New gadgets can be created and unnecessary ones deleted. More than one instance of the same gadget can be opened at the same time and each instance of the same gadget can have different settings. The gadgets instances are completely independent.
- </para>
+ <title>The Dashboard</title>
+ <para>
+ The Dashboard is used for hosting mini applications known as gadgets. The Dashboard uses a variety of graphical effects for displaying, opening and using gadgets.
+ </para>
+ <para>
+ The active Dashboard can be individually named by double clicking on the default name ("<emphasis>Click and Type Page Name</emphasis>")...
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Dashname.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Dashname.png" format="PNG" align="center" scalefit="1" contentwidth="120mm"/>
+ </imageobject>
+ </mediaobject>
+ <para>
+ ...and entering a new name:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Dashname1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Dashname1.png" format="PNG" align="center" scalefit="1" contentwidth="120mm"/>
+ </imageobject>
+ </mediaobject>
+ <para>
+ The Dashboard can also be tabbed to create multiple spaces. Open a new tab by clicking the <emphasis role="bold">+</emphasis> button beside the Dashboard name.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/tabbed_dash.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/tabbed_dash.png" format="PNG" align="center" contentwidth="110mm" />
+ </imageobject>
+ </mediaobject>
+ <para>
+ New tabs can also be individually named and managed.
+ </para>
+ <para>
+ Gadgets within the Dashboard can be moved and rearranged. New gadgets can be created and unnecessary ones deleted. More than one instance of the same gadget can be opened at the same time and each instance of the same gadget can have different settings. The gadgets instances are completely independent.
+ </para>
- <section id="sect-User_Guide-Dashboard_Portlet-Using_the_Dashboard_Workspace">
- <title>Using the Dashboard Workspace</title>
- <procedure>
- <step>
- <para>
- Click on <emphasis role="bold">Dashboard</emphasis> in the toolbar to access the Dashboard.
- </para>
- </step>
- <step>
- <para>
- Click on <emphasis role="bold">Add Gadgets</emphasis> to open the Dashboard Workspace.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scale="100" />
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
- </imageobject>
- </mediaobject>
- </step>
- </procedure>
- <para>
- The Dashboard Workspace lists all available gadgets. Four gadgets are provided by default with JBoss Enterprise Portal Platform, however you can add many more.
- </para>
+ <section id="sect-User_Guide-Dashboard_Portlet-Using_the_Dashboard_Workspace">
+ <title>Using the Dashboard Workspace</title>
+ <procedure>
+ <step>
+ <para>
+ Click on <emphasis role="bold">Dashboard</emphasis> in the toolbar to access the Dashboard.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click on <emphasis role="bold">Add Gadgets</emphasis> to open the Dashboard Workspace.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scale="100" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
+ </imageobject>
+ </mediaobject>
+ </step>
+ </procedure>
+ <para>
+ The Dashboard Workspace lists all available gadgets. Four gadgets are provided by default with JBoss Enterprise Portal Platform, however you can add many more.
+ </para>
<mediaobject>
<imageobject role="html">
<imagedata fileref="images/Dash_Workspace.png" format="PNG" align="center" scale="100" />
@@ -81,201 +81,201 @@
<imagedata fileref="images/Dash_Workspace.png" format="PNG" align="center" contentwidth="70mm" />
</imageobject>
</mediaobject>
- <variablelist id="vari-User_Guide-Using_the_Dashboard_Workspace-Default_Gadgets">
- <title>Default Gadgets:</title>
- <varlistentry>
- <term><emphasis role="bold">Calendar</emphasis></term>
- <listitem>
- <para>
- The calendar gadget helps track and plan your events and activities.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Calendar.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Calendar.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
- </imageobject>
- </mediaobject>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Todo</emphasis></term>
- <listitem>
- <para>
- This application helps you organize your day and work group. It is designed to keep track of your tasks in a convenient and transparent way.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Todo.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Todo.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
- </imageobject>
- </mediaobject>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">Calculator</emphasis></term>
- <listitem>
- <para>
- This mini-application lets you perform most basic arithmetic operations and can be themed to match the rest of your portal.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Calculator.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Calculator.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
- </imageobject>
- </mediaobject>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><emphasis role="bold">RSS Reader</emphasis></term>
- <listitem>
- <para>
- An RSS reader, or aggregator, collates content from various, user-specified feed sources and displays them in one location. This content can include, but isn't limited to, news headlines, blog posts or email. The RSS Reader gadget displays this content in a single window on your Portal page.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/RSSReader.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/RSSReader.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
- </imageobject>
- </mediaobject>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- To use one of the default gadgets, simply drag it from the <emphasis role="bold">Dashboard Workspace</emphasis> onto your Dashboard as illustrated below:
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Dash2.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Dash2.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
- </imageobject>
- </mediaobject>
- </section>
-
- <section id="sect-User_Guide-Dashboard_Portlet-Add_Gadgets">
- <title>Add Gadgets</title>
- <para>
- Many more gadgets can be found at <ulink type="http" url="http://www.google.com/ig/directory?synd=open">Google Gadgets</ulink>. JBoss Enterprise Portal Platform is compatible with most of the gadgets available there.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/GoogleGadgets.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/GoogleGadgets.png" format="PNG" align="center" scalefit="1" contentwidth="160mm"/>
- </imageobject>
- </mediaobject>
+ <variablelist id="vari-User_Guide-Using_the_Dashboard_Workspace-Default_Gadgets">
+ <title>Default Gadgets:</title>
+ <varlistentry>
+ <term><emphasis role="bold">Calendar</emphasis></term>
+ <listitem>
+ <para>
+ The calendar gadget helps track and plan your events and activities.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Calendar.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Calendar.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Todo</emphasis></term>
+ <listitem>
+ <para>
+ This application helps you organize your day and work group. It is designed to keep track of your tasks in a convenient and transparent way.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Todo.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Todo.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">Calculator</emphasis></term>
+ <listitem>
+ <para>
+ This mini-application lets you perform most basic arithmetic operations and can be themed to match the rest of your portal.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Calculator.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Calculator.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><emphasis role="bold">RSS Reader</emphasis></term>
+ <listitem>
+ <para>
+ An RSS reader, or aggregator, collates content from various, user-specified feed sources and displays them in one location. This content can include, but isn't limited to, news headlines, blog posts or email. The RSS Reader gadget displays this content in a single window on your Portal page.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/RSSReader.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/RSSReader.png" format="PNG" align="center" scalefit="1" contentwidth="70mm"/>
+ </imageobject>
+ </mediaobject>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ To use one of the default gadgets, simply drag it from the <emphasis role="bold">Dashboard Workspace</emphasis> onto your Dashboard as illustrated below:
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Dash2.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Dash2.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
+ </imageobject>
+ </mediaobject>
+ </section>
+
+ <section id="sect-User_Guide-Dashboard_Portlet-Add_Gadgets">
+ <title>Add Gadgets</title>
+ <para>
+ Many more gadgets can be found at <ulink type="http" url="http://www.google.com/ig/directory?synd=open">Google Gadgets</ulink>. JBoss Enterprise Portal Platform is compatible with most of the gadgets available there.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/GoogleGadgets.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/GoogleGadgets.png" format="PNG" align="center" scalefit="1" contentwidth="160mm"/>
+ </imageobject>
+ </mediaobject>
- <para>
- To add gadgets from external sources:
- </para>
- <procedure>
- <step>
- <para>
- Obtain the URL (<emphasis>.xml</emphasis> or <emphasis>.rss</emphasis>) of the gadget you wish to add from the gadget source.
- </para>
- <para>
- The gadgets available at <ulink type="http" url="http://www.google.com/ig/directory?synd=open">Google Gadget</ulink> provide a link to <emphasis role="bold">View source</emphasis>. Clicking on this link will open a page showing the gadget's XML source. Use the URL of this page in the Dashboard Workspace. The URL should end with <literal>.xml</literal>
- </para>
- <para>
- For example:
- </para>
+ <para>
+ To add gadgets from external sources:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Obtain the URL (<emphasis>.xml</emphasis> or <emphasis>.rss</emphasis>) of the gadget you wish to add from the gadget source.
+ </para>
+ <para>
+ The gadgets available at <ulink type="http" url="http://www.google.com/ig/directory?synd=open">Google Gadget</ulink> provide a link to <emphasis role="bold">View source</emphasis>. Clicking on this link will open a page showing the gadget's XML source. Use the URL of this page in the Dashboard Workspace. The URL should end with <literal>.xml</literal>
+ </para>
+ <para>
+ For example:
+ </para>
<programlisting>
http://www.donalobrien.net/apps/google/currency.xml
</programlisting>
- <note>
- <title>URL Types</title>
- <para>
- Remote gadgets can be only created using an .xml link or RSS URL. However, if you use a link that generates an RSS feed (for example: <ulink type="http" url="http://feeds.feedburner.com/gatein">http://feeds.feedburner.com/gatein</ulink>), a new RSS reader gadget will be created automatically even if the URL does not end with <literal>.rss</literal>.
- </para>
- </note>
- </step>
- <step>
- <para>
- Return to your portal and click <emphasis role="bold">Dashboard</emphasis> in the toolbar.
- </para>
+ <note>
+ <title>URL Types</title>
+ <para>
+ Remote gadgets can be only created using an .xml link or RSS URL. However, if you use a link that generates an RSS feed (for example: <ulink type="http" url="http://feeds.feedburner.com/gatein">http://feeds.feedburner.com/gatein</ulink>), a new RSS reader gadget will be created automatically even if the URL does not end with <literal>.rss</literal>.
+ </para>
+ </note>
+ </step>
+ <step>
+ <para>
+ Return to your portal and click <emphasis role="bold">Dashboard</emphasis> in the toolbar.
+ </para>
<!--
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/DashboardLink.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/DashboardLink.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
- </imageobject>
- </mediaobject>
--->
- </step>
- <step>
- <para>
- Click on <emphasis role="bold">Add Gadgets</emphasis> in the Dashboard to open the Dashboard Workspace.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scalefit="1" contentwidth="90mm"/>
- </imageobject>
- </mediaobject>
- </step>
- <step>
- <para>
- The Dashboard Workspace dialog appears:
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/EnterLink.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/EnterLink.png" format="PNG" align="center" scalefit="1" contentwidth="50mm"/>
- </imageobject>
- </mediaobject>
- </para>
- </step>
- <step>
- <para>
- Paste the URL obtained in step 1 into the text box above the gadget list.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/CodePaste.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/CodePaste.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
- </imageobject>
- </mediaobject>
-
- </step>
- <step>
- <para>
- Click on the <emphasis role="bold">plus</emphasis> icon to add the new gadget to the page.
- </para>
- <para>
- The new gadget will appear on the Dashboard alongside any other gadgets already in use. If required, the new gadget can be dragged to another position on the page.
- </para>
- <para>
- In the image below, the Currency Converter gadget has been added to the Dashboard, along with some of the default portal gadgets.
- </para>
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/NewGadget.png" format="PNG" align="center" scale="100"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/NewGadget.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
- </imageobject>
- </mediaobject>
- </step>
- </procedure>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/DashboardLink.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/DashboardLink.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
+ </imageobject>
+ </mediaobject>
+-->
+ </step>
+ <step>
+ <para>
+ Click on <emphasis role="bold">Add Gadgets</emphasis> in the Dashboard to open the Dashboard Workspace.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/Dashboard1.png" format="PNG" align="center" scalefit="1" contentwidth="90mm"/>
+ </imageobject>
+ </mediaobject>
+ </step>
+ <step>
+ <para>
+ The Dashboard Workspace dialog appears:
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/EnterLink.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/EnterLink.png" format="PNG" align="center" scalefit="1" contentwidth="50mm"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </step>
+ <step>
+ <para>
+ Paste the URL obtained in step 1 into the text box above the gadget list.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/CodePaste.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/CodePaste.png" format="PNG" align="center" scalefit="1" contentwidth="100mm" />
+ </imageobject>
+ </mediaobject>
+
+ </step>
+ <step>
+ <para>
+ Click on the <emphasis role="bold">plus</emphasis> icon to add the new gadget to the page.
+ </para>
+ <para>
+ The new gadget will appear on the Dashboard alongside any other gadgets already in use. If required, the new gadget can be dragged to another position on the page.
+ </para>
+ <para>
+ In the image below, the Currency Converter gadget has been added to the Dashboard, along with some of the default portal gadgets.
+ </para>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/NewGadget.png" format="PNG" align="center" scale="100"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/NewGadget.png" format="PNG" align="center" scalefit="1" contentwidth="150mm"/>
+ </imageobject>
+ </mediaobject>
+ </step>
+ </procedure>
- </section>
+ </section>
</section>
Added: epp/docs/branches/5.1/User_Guide/en-US/modules/terms/Portlet_container_concept.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/modules/terms/Portlet_container_concept.xml (rev 0)
+++ epp/docs/branches/5.1/User_Guide/en-US/modules/terms/Portlet_container_concept.xml 2011-08-11 04:41:47 UTC (rev 7044)
@@ -0,0 +1,20 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "../../User_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-User_Guide-Portlet_Container">
+ <title>Portlet Container</title>
+<!-- Source Metadata
+URL: http://download.oracle.com/docs/cd/B14099_19/core.1012/b13994/glossary.ht...
+URL: http://publib.boulder.ibm.com/infocenter/wasinfo/beta/index.jsp?topic=%2F...
+URL:
+-->
+<!-- Added to satisfy https://bugzilla.redhat.com/show_bug.cgi?id=692170 -->
+ <para>
+ A portlet container supplies the runtime environment in which portlets are started, run and ended. While portlet containers can allow portlets to inherit data from the main portal they also provide an environment in which portlets can be independently managed. APIs dictate both how a portal interacts with portlet containers and how portlet containers interact with individual portlets.
+ </para>
+ <para>
+
+ </para>
+</section>
\ No newline at end of file
Modified: epp/docs/branches/5.1/User_Guide/publican.cfg
===================================================================
--- epp/docs/branches/5.1/User_Guide/publican.cfg 2011-08-11 04:36:00 UTC (rev 7043)
+++ epp/docs/branches/5.1/User_Guide/publican.cfg 2011-08-11 04:41:47 UTC (rev 7044)
@@ -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.1-web-__LANG__
\ No newline at end of file
13 years, 4 months
- 1
- 0
gatein SVN: r7043 - portal/trunk/testsuite/selenium-snifftests.
by do-not-reply＠jboss.org
Author: hangnguyen
Date: 2011-08-11 00:36:00 -0400 (Thu, 11 Aug 2011)
New Revision: 7043
Modified:
portal/trunk/testsuite/selenium-snifftests/pom.xml
Log:
TESTVN-4010: add ISO-8859-1 in pom.xml
Modified: portal/trunk/testsuite/selenium-snifftests/pom.xml
===================================================================
--- portal/trunk/testsuite/selenium-snifftests/pom.xml 2011-08-10 17:51:44 UTC (rev 7042)
+++ portal/trunk/testsuite/selenium-snifftests/pom.xml 2011-08-11 04:36:00 UTC (rev 7043)
@@ -1,178 +1,193 @@
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
- <modelVersion>4.0.0</modelVersion>
- <parent>
- <groupId>org.exoplatform.portal</groupId>
- <artifactId>exo.portal.testsuite</artifactId>
- <version>3.2.0-M02-SNAPSHOT</version>
- </parent>
-
- <artifactId>exo.portal.selenium.snifftests</artifactId>
- <packaging>jar</packaging>
- <name>Selenium Sniff Test for GateIn</name>
- <description>Minimal UI tests that should work for GateIn</description>
-
- <properties>
- <org.selenium.server.version>1.0.1</org.selenium.server.version>
- <selenium.port>4444</selenium.port>
- <selenium.browser>firefox</selenium.browser>
- <selenium.timeout>10000</selenium.timeout>
- <selenium.speed>300</selenium.speed>
- <selenium.host>localhost</selenium.host>
- <org.selenium.maven-plugin.version>1.0.1</org.selenium.maven-plugin.version>
- </properties>
-
- <dependencies>
- <dependency>
- <groupId>junit</groupId>
- <artifactId>junit</artifactId>
- <version>4.0</version>
- </dependency>
-
- <dependency>
- <groupId>org.seleniumhq.selenium.client-drivers</groupId>
- <artifactId>selenium-java-client-driver</artifactId>
- <version>${org.selenium.server.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.seleniumhq.selenium.server</groupId>
- <artifactId>selenium-server</artifactId>
- <version>${org.selenium.server.version}</version>
- </dependency>
-
- <dependency>
- <groupId>commons-io</groupId>
- <artifactId>commons-io</artifactId>
- <version>1.4</version>
- </dependency>
- <dependency>
- <groupId>commons-lang</groupId>
- <artifactId>commons-lang</artifactId>
- <version>2.4</version>
- </dependency>
- </dependencies>
-
- <profiles>
- <profile>
- <id>selenium</id>
- <build>
- <plugins>
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>build-helper-maven-plugin</artifactId>
- <executions>
- <execution>
- <id>add-test-source</id>
- <phase>generate-sources</phase>
- <goals>
- <goal>add-test-source</goal>
- </goals>
- <configuration>
- <sources>
- <source>${project.build.directory}/generated/test</source>
- </sources>
- </configuration>
- </execution>
- </executions>
- </plugin>
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>exec-maven-plugin</artifactId>
- <executions>
- <execution>
- <phase>generate-test-sources</phase>
- <goals>
- <goal>java</goal>
- </goals>
- </execution>
- </executions>
- <configuration>
- <mainClass>org.exoplatform.portal.selenium.SeleniumTestCaseGenerator</mainClass>
- <arguments>
- <argument>${project.basedir}/src/suite</argument>
- <argument>${project.build.directory}/generated/test</argument>
- </arguments>
- </configuration>
- </plugin>
-
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>selenium-maven-plugin</artifactId>
- <version>${org.selenium.maven-plugin.version}</version>
- <executions>
- <execution>
- <phase>pre-integration-test</phase>
- <goals>
- <goal>start-server</goal>
- </goals>
- <configuration>
- <background>true</background>
- <logFile>${project.build.directory}/server.log</logFile>
- <logOutput>true</logOutput>
- <userExtensions>${pom.basedir}/src/suite/user-extensions.js</userExtensions>
- <port>${selenium.port}</port>
- </configuration>
- </execution>
- </executions>
- </plugin>
-
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-plugin</artifactId>
- <executions>
- <execution>
- <phase>integration-test</phase>
- <goals>
- <goal>test</goal>
- </goals>
- <configuration>
- <skip>false</skip>
- <!--
- <includes><include>**/Test_UserExtensions.java</include></includes>
- -->
- <includes><include>**/selenium/Test_*.java</include></includes>
- <systemProperties>
- <property>
- <name>selenium.port</name>
- <value>${selenium.port}</value>
- </property>
- <property>
- <name>selenium.browser</name>
- <value>${selenium.browser}</value>
- </property>
- <property>
- <name>selenium.speed</name>
- <value>${selenium.speed}</value>
- </property>
- <property>
- <name>selenium.timeout</name>
- <value>${selenium.timeout}</value>
- </property>
- <property>
- <name>selenium.host</name>
- <value>${selenium.host}</value>
- </property>
- </systemProperties>
- </configuration>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
- </profile>
- </profiles>
-
- <!-- no tests by default -->
- <build>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-plugin</artifactId>
- <configuration>
- <skip>true</skip>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
-</project>
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <parent>
+ <groupId>org.exoplatform.portal</groupId>
+ <artifactId>exo.portal.testsuite</artifactId>
+ <version>3.2.0-M02-SNAPSHOT</version>
+ </parent>
+
+ <artifactId>exo.portal.selenium.snifftests</artifactId>
+ <packaging>jar</packaging>
+ <name>Selenium Sniff Test for GateIn</name>
+ <description>Minimal UI tests that should work for GateIn</description>
+
+ <properties>
+ <org.selenium.server.version>1.0.1</org.selenium.server.version>
+ <selenium.port>4444</selenium.port>
+ <selenium.browser>firefox</selenium.browser>
+ <selenium.timeout>10000</selenium.timeout>
+ <selenium.speed>300</selenium.speed>
+ <selenium.host>localhost</selenium.host>
+ <org.selenium.maven-plugin.version>1.0.1</org.selenium.maven-plugin.version>
+ </properties>
+
+ <dependencies>
+ <dependency>
+ <groupId>junit</groupId>
+ <artifactId>junit</artifactId>
+ <version>4.0</version>
+ </dependency>
+
+ <dependency>
+ <groupId>org.seleniumhq.selenium.client-drivers</groupId>
+ <artifactId>selenium-java-client-driver</artifactId>
+ <version>${org.selenium.server.version}</version>
+ </dependency>
+
+ <dependency>
+ <groupId>org.seleniumhq.selenium.server</groupId>
+ <artifactId>selenium-server</artifactId>
+ <version>${org.selenium.server.version}</version>
+ </dependency>
+
+ <dependency>
+ <groupId>commons-io</groupId>
+ <artifactId>commons-io</artifactId>
+ <version>1.4</version>
+ </dependency>
+ <dependency>
+ <groupId>commons-lang</groupId>
+ <artifactId>commons-lang</artifactId>
+ <version>2.4</version>
+ </dependency>
+ </dependencies>
+
+ <profiles>
+ <profile>
+ <id>selenium</id>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <configuration>
+ <encoding>ISO-8859-1</encoding>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>build-helper-maven-plugin</artifactId>
+ <executions>
+ <execution>
+ <id>add-test-source</id>
+ <phase>generate-sources</phase>
+ <goals>
+ <goal>add-test-source</goal>
+ </goals>
+ <configuration>
+ <sources>
+ <source>${project.build.directory}/generated/test</source>
+ </sources>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>exec-maven-plugin</artifactId>
+ <executions>
+ <execution>
+ <phase>generate-test-sources</phase>
+ <goals>
+ <goal>java</goal>
+ </goals>
+ </execution>
+ </executions>
+ <configuration>
+ <mainClass>org.exoplatform.portal.selenium.SeleniumTestCaseGenerator</mainClass>
+ <arguments>
+ <argument>${project.basedir}/src/suite</argument>
+ <argument>${project.build.directory}/generated/test</argument>
+ </arguments>
+ </configuration>
+ </plugin>
+
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>selenium-maven-plugin</artifactId>
+ <version>${org.selenium.maven-plugin.version}</version>
+ <executions>
+ <execution>
+ <phase>pre-integration-test</phase>
+ <goals>
+ <goal>start-server</goal>
+ </goals>
+ <configuration>
+ <background>true</background>
+ <logFile>${project.build.directory}/server.log</logFile>
+ <logOutput>true</logOutput>
+ <userExtensions>${pom.basedir}/src/suite/user-extensions.js</userExtensions>
+ <port>${selenium.port}</port>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-plugin</artifactId>
+ <executions>
+ <execution>
+ <phase>integration-test</phase>
+ <goals>
+ <goal>test</goal>
+ </goals>
+ <configuration>
+ <skip>false</skip>
+ <!--
+ <includes><include>**/Test_UserExtensions.java</include></includes>
+ -->
+ <includes><include>**/selenium/Test_*.java</include></includes>
+ <systemProperties>
+ <property>
+ <name>selenium.port</name>
+ <value>${selenium.port}</value>
+ </property>
+ <property>
+ <name>selenium.browser</name>
+ <value>${selenium.browser}</value>
+ </property>
+ <property>
+ <name>selenium.speed</name>
+ <value>${selenium.speed}</value>
+ </property>
+ <property>
+ <name>selenium.timeout</name>
+ <value>${selenium.timeout}</value>
+ </property>
+ <property>
+ <name>selenium.host</name>
+ <value>${selenium.host}</value>
+ </property>
+ </systemProperties>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+ </profiles>
+
+ <!-- no tests by default -->
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-plugin</artifactId>
+ <configuration>
+ <skip>true</skip>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <configuration>
+ <encoding>UTF-8</encoding>
+ </configuration>
+ </plugin>
+
+ </plugins>
+ </build>
+
+</project>
13 years, 4 months
- 1
- 0
gatein SVN: r7042 - portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/management/operations/navigation.
by do-not-reply＠jboss.org
Author: nscavell
Date: 2011-08-10 13:51:44 -0400 (Wed, 10 Aug 2011)
New Revision: 7042
Modified:
portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/management/operations/navigation/NavigationUtils.java
Log:
GTNPORTAL-1995: Invalid parent uri while exporting navigation fragment.
Modified: portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/management/operations/navigation/NavigationUtils.java
===================================================================
--- portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/management/operations/navigation/NavigationUtils.java 2011-08-10 13:40:33 UTC (rev 7041)
+++ portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/management/operations/navigation/NavigationUtils.java 2011-08-10 17:51:44 UTC (rev 7042)
@@ -123,7 +123,7 @@
children.add(createPageNode(service, node));
NavigationFragment fragment = new NavigationFragment();
- StringBuilder parentUri = new StringBuilder("/");
+ StringBuilder parentUri = new StringBuilder("");
getPath(node.getParent(), parentUri);
fragment.setParentURI(parentUri.toString());
fragment.setNodes(children);
@@ -138,7 +138,7 @@
if (node == null) return;
if (node.getParent() == null) return; // since "default" is the root node, we ignore it
- parentUri.insert(0, node.getName()).append("/");
+ parentUri.insert(0, node.getName()).insert(0, "/");
getPath(node.getParent(), parentUri);
}
13 years, 4 months
- 1
- 0
gatein SVN: r7041 - epp/portal/branches/EPP_5_1_Branch/portlet/exoadmin/src/main/java/org/exoplatform/applicationregistry/webui/component.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-08-10 09:40:33 -0400 (Wed, 10 Aug 2011)
New Revision: 7041
Modified:
epp/portal/branches/EPP_5_1_Branch/portlet/exoadmin/src/main/java/org/exoplatform/applicationregistry/webui/component/UICategoryForm.java
Log:
JBEPP-997 XSS issue in category description
Modified: epp/portal/branches/EPP_5_1_Branch/portlet/exoadmin/src/main/java/org/exoplatform/applicationregistry/webui/component/UICategoryForm.java
===================================================================
--- epp/portal/branches/EPP_5_1_Branch/portlet/exoadmin/src/main/java/org/exoplatform/applicationregistry/webui/component/UICategoryForm.java 2011-08-10 09:37:17 UTC (rev 7040)
+++ epp/portal/branches/EPP_5_1_Branch/portlet/exoadmin/src/main/java/org/exoplatform/applicationregistry/webui/component/UICategoryForm.java 2011-08-10 13:40:33 UTC (rev 7041)
@@ -41,6 +41,7 @@
import org.exoplatform.webui.form.validator.StringLengthValidator;
import org.exoplatform.webui.organization.UIListPermissionSelector;
import org.exoplatform.webui.organization.UIListPermissionSelector.EmptyIteratorValidator;
+import org.gatein.common.text.EntityEncoder;
import java.util.ArrayList;
import java.util.Date;
@@ -104,7 +105,7 @@
category_ = category;
uiSetting.getUIStringInput(FIELD_NAME).setEditable(false).setValue(category_.getName());
uiSetting.getUIStringInput(FIELD_DISPLAY_NAME).setValue(category_.getDisplayName());
- uiSetting.getUIFormTextAreaInput(FIELD_DESCRIPTION).setValue(category_.getDescription());
+ uiSetting.getUIFormTextAreaInput(FIELD_DESCRIPTION).setValue( EntityEncoder.FULL.encode(category_.getDescription()) );
List<String> accessPermissions = category_.getAccessPermissions();
String[] per = new String[accessPermissions.size()];
if (accessPermissions != null && accessPermissions.size() > 0)
13 years, 4 months
- 1
- 0
gatein SVN: r7040 - in portal/trunk: portlet/dashboard/src/main/webapp/groovy/gadget/webui/component and 1 other directories.
by do-not-reply＠jboss.org
Author: ndkhoiits
Date: 2011-08-10 05:37:17 -0400 (Wed, 10 Aug 2011)
New Revision: 7040
Modified:
portal/trunk/portlet/dashboard/src/main/java/org/exoplatform/gadget/webui/component/UIGadgetPortlet.java
portal/trunk/portlet/dashboard/src/main/webapp/groovy/gadget/webui/component/UIGadgetViewMode.gtmpl
portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/ModelAdapter.java
portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/UIPortlet.java
Log:
GTNPORTAL-1860 support for saving gadget portlet wrapper preferences withing the gadget
Modified: portal/trunk/portlet/dashboard/src/main/java/org/exoplatform/gadget/webui/component/UIGadgetPortlet.java
===================================================================
--- portal/trunk/portlet/dashboard/src/main/java/org/exoplatform/gadget/webui/component/UIGadgetPortlet.java 2011-08-10 08:46:33 UTC (rev 7039)
+++ portal/trunk/portlet/dashboard/src/main/java/org/exoplatform/gadget/webui/component/UIGadgetPortlet.java 2011-08-10 09:37:17 UTC (rev 7040)
@@ -26,6 +26,7 @@
import org.exoplatform.container.ExoContainerContext;
import org.exoplatform.portal.webui.application.GadgetUtil;
import org.exoplatform.web.application.ApplicationMessage;
+import org.exoplatform.webui.application.WebuiApplication;
import org.exoplatform.webui.application.WebuiRequestContext;
import org.exoplatform.webui.application.portlet.PortletRequestContext;
import org.exoplatform.webui.config.annotation.ComponentConfig;
@@ -38,6 +39,7 @@
import org.json.JSONObject;
import javax.portlet.PortletPreferences;
+import javax.portlet.PortletRequest;
/**
* Created by The eXo Platform SARL
@@ -52,11 +54,48 @@
private static final Logger log = LoggerFactory.getLogger(GadgetImporter.class);
+ /** User pref. */
+ private String userPref;
+
public UIGadgetPortlet() throws Exception
{
addChild(UIGadgetViewMode.class, null, null);
}
+
+ public String getUserPref()
+ {
+ return userPref;
+ }
+ @Override
+ public void processAction(WebuiRequestContext context) throws Exception
+ {
+ super.processAction(context);
+
+ //
+ PortletRequest req = context.getRequest();
+
+ //
+ userPref = req.getParameter("userPref");
+ if (userPref != null && !userPref.isEmpty())
+ {
+ PortletPreferences prefs = req.getPreferences();
+ prefs.setValue("userPref", userPref);
+ prefs.store();
+ }
+ }
+
+ @Override
+ public void processRender(WebuiApplication app, WebuiRequestContext context) throws Exception
+ {
+ PortletRequest req = context.getRequest();
+ PortletPreferences prefs = req.getPreferences();
+ userPref = prefs.getValue("userPref", null);
+
+ //
+ super.processRender(app, context);
+ }
+
public String getUrl()
{
PortletRequestContext pcontext = (PortletRequestContext)WebuiRequestContext.getCurrentInstance();
Modified: portal/trunk/portlet/dashboard/src/main/webapp/groovy/gadget/webui/component/UIGadgetViewMode.gtmpl
===================================================================
--- portal/trunk/portlet/dashboard/src/main/webapp/groovy/gadget/webui/component/UIGadgetViewMode.gtmpl 2011-08-10 08:46:33 UTC (rev 7039)
+++ portal/trunk/portlet/dashboard/src/main/webapp/groovy/gadget/webui/component/UIGadgetViewMode.gtmpl 2011-08-10 09:37:17 UTC (rev 7040)
@@ -12,7 +12,7 @@
if(url != null) {
def metadata = uicomponent.getParent().getMetadata(url);
- def userPref = null;
+ def userPref = uicomponent.getParent().getUserPref();
JavascriptManager jsmanager = rcontext.getJavascriptManager();
jsmanager.importJavascript("eXo.gadget.UIGadget") ;
jsmanager.addCustomizedOnLoadScript("eXo.gadget.UIGadget.createGadget('$url','$id', $metadata, $userPref, 'canvas', '$hostName');") ;
Modified: portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/ModelAdapter.java
===================================================================
--- portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/ModelAdapter.java 2011-08-10 08:46:33 UTC (rev 7039)
+++ portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/ModelAdapter.java 2011-08-10 09:37:17 UTC (rev 7040)
@@ -27,7 +27,6 @@
import org.exoplatform.portal.config.model.TransientApplicationState;
import org.exoplatform.portal.pc.ExoPortletState;
import org.exoplatform.portal.pc.ExoPortletStateType;
-import org.exoplatform.portal.pom.config.Utils;
import org.exoplatform.portal.pom.spi.gadget.Gadget;
import org.exoplatform.portal.pom.spi.portlet.Portlet;
import org.exoplatform.portal.pom.spi.portlet.PortletBuilder;
@@ -40,6 +39,7 @@
import java.io.Serializable;
import java.util.Arrays;
+import java.util.Collections;
import java.util.List;
import java.util.Map;
@@ -204,6 +204,12 @@
String url = GadgetUtil.reproduceUrl(model.getUrl(), model.isLocal());
ExoPortletState prefs = new ExoPortletState(WRAPPER_ID);
prefs.getState().put("url", Arrays.asList(url));
+ DataStorage dataStorage = (DataStorage)container.getComponentInstanceOfType(DataStorage.class);
+ Gadget gadget = dataStorage.load(applicationState, ApplicationType.GADGET);
+ if (gadget != null && gadget.getUserPref() != null)
+ {
+ prefs.getState().put("userPref", Collections.singletonList(gadget.getUserPref()));
+ }
return StatefulPortletContext.create(LOCAL_STATE_ID, ExoPortletStateType.getInstance(), prefs);
}
@@ -211,7 +217,33 @@
public ApplicationState<Gadget> update(ExoContainer container, ExoPortletState updateState,
ApplicationState<Gadget> gadgetApplicationState) throws Exception
{
- throw new UnsupportedOperationException("Cannot edit gadget preferences");
+ // Compute new preferences
+ String userPref = null;
+ for (Map.Entry<String, List<String>> entry : updateState.getState().entrySet())
+ {
+ if (entry.getKey().equals("userPref") && entry.getValue().size() > 0)
+ {
+ userPref = entry.getValue().get(0);
+ }
+ }
+
+ if (gadgetApplicationState instanceof TransientApplicationState<?>)
+ {
+ throw new UnsupportedOperationException("todo");
+ }
+ else
+ {
+ if (userPref != null)
+ {
+ Gadget gadget = new Gadget();
+ gadget.addUserPref(userPref);
+ DataStorage dataStorage = (DataStorage)container.getComponentInstanceOfType(DataStorage.class);
+ dataStorage.save(gadgetApplicationState, gadget);
+ }
+ }
+
+ //
+ return gadgetApplicationState;
}
@Override
Modified: portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/UIPortlet.java
===================================================================
--- portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/UIPortlet.java 2011-08-10 08:46:33 UTC (rev 7039)
+++ portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/application/UIPortlet.java 2011-08-10 09:37:17 UTC (rev 7040)
@@ -52,7 +52,6 @@
import org.gatein.common.net.media.MediaType;
import org.gatein.common.util.ParameterValidation;
import org.gatein.pc.api.Mode;
-import org.gatein.pc.api.NoSuchPortletException;
import org.gatein.pc.api.PortletContext;
import org.gatein.pc.api.PortletInvoker;
import org.gatein.pc.api.PortletInvokerException;
@@ -1003,7 +1002,8 @@
public void update(C updateState) throws Exception
{
WebuiRequestContext context = WebuiRequestContext.getCurrentInstance();
- ExoContainer container = context.getApplication().getApplicationServiceContainer(); state.setApplicationState(adapter.update(container, updateState, state.getApplicationState()));
+ ExoContainer container = context.getApplication().getApplicationServiceContainer();
+ state.setApplicationState(adapter.update(container, updateState, state.getApplicationState()));
setState(state);
}
13 years, 4 months
- 1
- 0
gatein SVN: r7039 - in epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp: src and 1 other directory.
by do-not-reply＠jboss.org
Author: hfnukal
Date: 2011-08-10 04:46:33 -0400 (Wed, 10 Aug 2011)
New Revision: 7039
Modified:
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml
epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/assemble.xml
Log:
JBEPP-1004 Clustering not working with buddy replication enabled
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-08-10 07:03:33 UTC (rev 7038)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-08-10 08:46:33 UTC (rev 7039)
@@ -293,6 +293,14 @@
<artifactId>commons-collections</artifactId>
<groupId>commons-collections</groupId>
</exclusion>
+ <exclusion>
+ <artifactId>infinispan-cachestore-jdbc</artifactId>
+ <groupId>org.infinispan</groupId>
+ </exclusion>
+ <exclusion>
+ <artifactId>infinispan-core</artifactId>
+ <groupId>org.infinispan</groupId>
+ </exclusion>
</exclusions>
</dependency>
<dependency>
@@ -692,6 +700,14 @@
<artifactId>commons-collections</artifactId>
<groupId>commons-collections</groupId>
</exclusion>
+ <exclusion>
+ <artifactId>infinispan-core</artifactId>
+ <groupId>org.infinispan</groupId>
+ </exclusion>
+ <exclusion>
+ <artifactId>infinispan-cachestore-jdbc</artifactId>
+ <groupId>org.infinispan</groupId>
+ </exclusion>
</exclusions>
</dependency>
<dependency>
Modified: epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/assemble.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/assemble.xml 2011-08-10 07:03:33 UTC (rev 7038)
+++ epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/src/assemble.xml 2011-08-10 08:46:33 UTC (rev 7039)
@@ -15,49 +15,55 @@
<includes>
<include>*.distribution.deploy:*:zip</include>
</includes>
- <excludes>
- <exclude>*:hibernate-core:3.3.2.GA:jar</exclude>
- <exclude>*:jaxb-api:2.1:jar</exclude>
- <exclude>*:stax-api:1.0:jar</exclude>
- </excludes>
<outputDirectory>${eap.dir}/jboss-as/server/default</outputDirectory>
<unpack>true</unpack>
+ <unpackOptions>
+ <excludes>
+ <exclude>**/hibernate-core*</exclude>
+ <exclude>**/jaxb-api*</exclude>
+ <exclude>**/stax-api*</exclude>
+ </excludes>
+ </unpackOptions>
</dependencySet>
<dependencySet>
<includes>
<include>*.distribution.deploy:*:zip</include>
</includes>
- <excludes>
- <exclude>*:hibernate-core:3.3.2.GA:jar</exclude>
- <exclude>*:jaxb-api:2.1:jar</exclude>
- <exclude>*:stax-api:1.0:jar</exclude>
-
- <!-- Exclude cluster -->
- <exclude>*:hibernate-jbosscache2:3.3.2.GA:jar</exclude>
- <exclude>*:jbosscache-core:3.2.6.GA:jar</exclude>
- <exclude>*:jgroups:2.6.13.GA:jar</exclude>
- </excludes>
<outputDirectory>${eap.dir}/jboss-as/server/all</outputDirectory>
<unpack>true</unpack>
+ <unpackOptions>
+ <excludes>
+ <exclude>**/hibernate-core*</exclude>
+ <exclude>**/jaxb-api*</exclude>
+ <exclude>**/stax-api*</exclude>
+
+ <!-- Exclude cluster -->
+ <exclude>**/hibernate-jbosscache2*</exclude>
+ <exclude>**/jbosscache-core*</exclude>
+ <exclude>**/jgroups*</exclude>
+ </excludes>
+ </unpackOptions>
</dependencySet>
<dependencySet>
<includes>
<include>*.distribution.deploy:*:zip</include>
</includes>
- <excludes>
- <exclude>*:hibernate-core:3.3.2.GA:jar</exclude>
- <exclude>*:jaxb-api:2.1:jar</exclude>
- <exclude>*:stax-api:1.0:jar</exclude>
-
- <!-- Exclude cluster -->
- <exclude>*:hibernate-jbosscache2:3.3.2.GA:jar</exclude>
- <exclude>*:jbosscache-core:3.2.6.GA:jar</exclude>
- <exclude>*:jgroups:2.6.13.GA:jar</exclude>
- </excludes>
<outputDirectory>${eap.dir}/jboss-as/server/production</outputDirectory>
<unpack>true</unpack>
+ <unpackOptions>
+ <excludes>
+ <exclude>**/hibernate-core*</exclude>
+ <exclude>**/jaxb-api*</exclude>
+ <exclude>**/stax-api*</exclude>
+
+ <!-- Exclude cluster -->
+ <exclude>**/hibernate-jbosscache2*</exclude>
+ <exclude>**/jbosscache-core*</exclude>
+ <exclude>**/jgroups*</exclude>
+ </excludes>
+ </unpackOptions>
</dependencySet>
<!-- END profiles -->
13 years, 4 months
- 1
- 0
gatein SVN: r7038 - epp/docs/branches/5.1/Release_Notes/en-US.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-10 03:03:33 -0400 (Wed, 10 Aug 2011)
New Revision: 7038
Modified:
epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml
epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml
epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
Log:
Updated with new issues for 5.1.1 release
Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -21,6 +21,22 @@
<variablelist id="vari-5.1.1_Release_Notes-New_and_Upgraded_Components-Upgraded_Components">
<title></title>
+ <varlistentry>
+ <term>eXo Kernel</term>
+ <listitem>
+ <para>
+ The eXo Kernel component has been upgraded to version 2.2.9-GA
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>eXo Core</term>
+ <listitem>
+ <para>
+ The eXo Core component has been upgraded to version 2.3.9-GA
+ </para>
+ </listitem>
+ </varlistentry>
<varlistentry>
<term>JBoss EAP</term>
<listitem>
@@ -49,7 +65,7 @@
<term>eXo JCR</term>
<listitem>
<para>
- The eXo Java Content Repository has been upgraded to version 1.12.8-GA. <!--JBEPP-728-->
+ The eXo Java Content Repository has been upgraded to version 1.12.9. <!--JBEPP-996-->
</para>
</listitem>
</varlistentry>
@@ -57,7 +73,7 @@
<term>PicketLink</term>
<listitem>
<para>
- The PicketLink IDM component has been upgraded to version 1.1.8-GA. <!--JBEPP-858-->
+ The PicketLink IDM component has been upgraded to version 1.1.9-GA. <!--JBEPP-858-->
</para>
</listitem>
</varlistentry>
@@ -65,7 +81,7 @@
<term>Seam</term>
<listitem>
<para>
- Seam has been upgraded to 2.2.3.EAP5 (as part of the EAP upgrade).
+ Seam has been upgraded to 2.2.4.EAP5 (as part of the EAP upgrade).
</para>
</listitem>
</varlistentry>
@@ -77,6 +93,14 @@
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>Portlet Bridge</term>
+ <listitem>
+ <para>
+ The Portlet Bridge component has been upgraded to version 2.1.2.GA.EPP51
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
<para>
More details about the component versions that make up JBoss Enterprise Portal Platform 5.1.1 can be found in <xref linkend="sect-5.1.1_Release_Notes-Component_Versions"/>
@@ -128,7 +152,7 @@
eXo kernel
</entry>
<entry>
- 2.2.8-GA
+ 2.2.9-GA
</entry>
</row>
<row>
@@ -136,7 +160,7 @@
eXo Core
</entry>
<entry>
- 2.3.8-GA
+ 2.3.9-GA
</entry>
</row>
<row>
@@ -152,7 +176,7 @@
eXo JCR
</entry>
<entry>
- 1.12.9
+ 1.12.9-GA
</entry>
</row>
<row>
@@ -240,7 +264,7 @@
PicketLink IDM
</entry>
<entry>
- 1.1.8.GA
+ 1.1.9.GA
</entry>
</row>
<row>
@@ -256,7 +280,7 @@
Portlet Bridge
</entry>
<entry>
- 2.1.1.GA.EPP51
+ 2.1.2.GA.EPP51
</entry>
</row>
<row>
@@ -264,7 +288,7 @@
Seam
</entry>
<entry>
- 2.2.3.EAP5-13.ep5.el6
+ 2.2.4.EAP5
</entry>
</row>
<row>
@@ -356,15 +380,76 @@
</section>
<section>
- <title><remark>NEEDINFO</remark></title>
+ <title><remark>NEEDINFO Issues</remark></title>
<xi:include href="need_info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>
<section>
- <title><remark>Not Documented</remark></title>
+ <title><remark>Not Documented Issues</remark></title>
<xi:include href="not_documented.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>
-
+ <section>
+ <title>Security Related Issues</title>
+ <variablelist>
+ <title></title>
+ <!-- https://issues.jboss.org/browse/JBEPP-598 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-598" /></term>
+ <listitem>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ Security vulnerabilies arising from the execution of XSS javascript entered into various portal form fields have been eradicated in this release.
+ </para>
+ <para>
+ The resolution to this issue also resolves the following related JIRA issues:
+ <simplelist>
+ <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-847"></ulink></member>
+ <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-997"></ulink></member>
+ <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-914"></ulink></member>
+ <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-365"></ulink></member>
+ </simplelist>
+ </para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-597 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term>
+ <listitem>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ The name of a dashboard page entered by user was not properly encoded before being returned on the web browser. This allowed javascript snippets to be executed when creating a new page through the Portal Dashboard. The name of the page is now properly HTML encoded before being returned and javascript is no longer invoked when entered into page fields.
+ </para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-881" /></term>
+ <listitem>
+ <!-- Added on advice from Dave Jorm in the security team -->
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ It was found that JBoss Seam 2 did not properly block access to JBoss Expression Language (EL) constructs in page exception handling, allowing arbitrary Java methods to be executed. A remote attacker could use this flaw to execute arbitrary code via a specially-crafted URL provided to certain applications based on the JBoss Seam 2 framework.
+ </para>
+ <para>
+ This issue has been fixed in JBoss Enterprise Application Platform version 5.1.1, which is incorporated in this release of JBoss Enterprise Portal Platform.
+ </para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
<section>
<title>Recommended Practices</title>
<variablelist>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<edition>2.1</edition>
- <pubsnumber>5.1.2</pubsnumber>
+ <pubsnumber>5.1.6</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Enterprise Portal Platform &VX; 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.1/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -7,83 +7,121 @@
<title>Revision History</title>
<simpara>
<revhistory>
- <revision>
- <revnumber>2.1-5.1.2</revnumber>
- <date>Mon Jul 11 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added more resolved issues and 'Not Yet Documented' section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2.1-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
+ <revision>
+ <revnumber>2.1-5.1.6</revnumber>
+ <date>Wed Aug 10 2011</date>
<author>
<firstname>Scott</firstname>
<surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
+ <email></email>
</author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.3</revnumber>
- <date>Thu Jun 02 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added "Recommended Practices" section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Wed May 4 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Compiled full Resolved Issues list and added component version details.</member>
- </simplelist>
- </revdescription>
- </revision>
+ <revdescription>
+ <simplelist>
+ <member>Added CVE-2011-1484 to Securty section.</member>
+ <member>Corrected minor typographicl errors.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
<revision>
- <revnumber>1-1.0</revnumber>
- <date>Thu Apr 28 2011</date>
- <author>
+ <revnumber>2.1-5.1.4</revnumber>
+ <date>Tue Aug 9 2011</date>
+ <author>
<firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
+ <surname>Mumford</surname>
+ <email></email>
</author>
- <revdescription>
+ <revdescription>
<simplelist>
- <member>Initial draft of Release Notes created.</member>
-
+ <member>Rebuilt using broader JIRA filters.</member>
+ <member>Added Security Issues section.</member>
</simplelist>
-
</revdescription>
-
</revision>
-
+ <revision>
+ <revnumber>2.1-5.1.3</revnumber>
+ <date>Fri Aug 5 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Updated to incorporate further bug fixes.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>2.1-5.1.2</revnumber>
+ <date>Mon Jul 11 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Added more resolved issues and 'Not Yet Documented' section.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>2.1-5.1.1</revnumber>
+ <date>Monday June 27 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email>smumford(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Updated for 5.1.1 Release.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>1-1.3</revnumber>
+ <date>Thu Jun 02 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email>smumford(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Added "Recommended Practices" section.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>1-1.1</revnumber>
+ <date>Wed May 4 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email>smumford(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Compiled full Resolved Issues list and added component version details.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>1-1.0</revnumber>
+ <date>Thu Apr 28 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email>smumford(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Initial draft of Release Notes created.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
</revhistory>
-
</simpara>
</appendix>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -1,4 +1,20 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent">
+%BOOK_ENTITIES;
+]>
-<para>
-There are no known issues in this release.
-</para>
+<variablelist>
+ <title></title>
+ <varlistentry>
+ <term><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-927"></ulink></term>
+ <listitem>
+ <para>
+ Administrators and users should be aware that adding a gadget to any portal page other than the dashboard, will result in any user set preferences or modifications (adding entries to the TODO gadget, for example) <emphasis role="bold">not</emphasis> being saved in a persistant manner.
+ </para>
+ <para>
+ This limitation will be corrected in a later version of JBoss Enterprise Portal Platform.
+ </para>
+ </listitem>
+ </varlistentry>
+</variablelist>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -1,4 +1,62 @@
+<?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" [
+]>
-<para>
-There are no issues that require more information at this time.
-</para>
+
+<variablelist>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-764 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-764" /></term>
+ <listitem>
+
+
+ <para>
+ To isolate multiple clusters running on the same network, the JBoss Cache and JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to include partition name (-g) and multicast address (-u) properties used in JBoss Enterprise Application Platform.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-811 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-811" /></term>
+ <listitem>
+
+
+ <para>
+ Some caching and overwriting issues have been encountered when more than one portal user attempts to manipulate the same portal resource concurrently (by editing the same page at the same time, for example).
+
+This release of JBoss Enterprise Portal Platform includes multiple patches designed to mitigate the issue somewhat. However, this is a complex issue and further development will be required in later iterations to resolve it completely.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-874 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-874" /></term>
+ <listitem>
+
+
+ <para>
+ It was found that, in previous versions of JBoss Enterprise Portal Platform, using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException (internally, org.exoplatform.services.transaction.TransactionException caused by org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been corrected by ensuring that loading data into cache occurs outside the current transaction.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-884 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-884" /></term>
+ <listitem>
+
+
+ <para>
+ Changed level of error message for JS compressor
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+</variablelist>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/not_documented.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -1,20 +1,3 @@
-<?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-987 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-987" /></term>
- <listitem>
-
- <para>
-
- </para>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
+<para>
+All Issues are documented.
+</para>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-10 01:35:44 UTC (rev 7037)
+++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-10 07:03:33 UTC (rev 7038)
@@ -4,16 +4,17 @@
<variablelist>
-
+
<!-- https://issues.jboss.org/browse/JBEPP-400 -->
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-400" /></term>
<listitem>
-
+
+
<para>
Warning messages were found in the server log when starting JBoss Enterprise Portal Platform 5 without an active internet connection. This was because the Java EE Webservices Metadata Handler 2.0 schema was requested via the network at start up. The schema is now bundled with the WSRP which allows JBoss Enterprise Portal Platform to start without producing error messages if there is no internet connection.
</para>
-
+
</listitem>
</varlistentry>
@@ -21,11 +22,25 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-459" /></term>
<listitem>
+
+
+ <para>
+ A thread safety issue in the breadcrumb portlet could lead to NullPointerException under load.The issue has been fixed.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-566 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-566" /></term>
+ <listitem>
+
+
<para>
- A thread safety issue in the breadcrumb portlet could lead to NullPointerException under load.The issue has been fixed.
+ A bug which prompted users to "Save and Close" an Edit Portlet dialogue if a tab in the window was clicked but the mouse cursor was removed from the tab before the mouse button was released has been corrected in this release.
</para>
-
+
</listitem>
</varlistentry>
@@ -33,75 +48,80 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-568" /></term>
<listitem>
-
+
+
<para>
In previous releases of JBoss Enterprise Portal Platform, users found that, when creating sub-nodes of system nodes (portal navigation, group navigation, register etc.), these new nodes where not visible once created. This issue, and a related issue encountered when attempting to 'cut' sub-nodes of system nodes, have been resolved in this latest release.
</para>
-
+
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-597 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-723 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-723" /></term>
<listitem>
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- The name of a dashboard page entered by user was not properly encoded before being returned on the web browser. This allowed javascript snippets to be executed when creating a new page through the Portal Dashboard. The name of the page is now properly HTML encoded before being returned and javascript is no longer invoked when entered into page fields.
- </para>
- </warning>
-
+
+
+ <para>
+ A bug in the UIUserInGroup.setValues() code caused previous versions of JBoss Enterprise Portal Platform to throw an error when users attempted to navigate to a new page withing the Group management view of the Organization portlet by any method other than the page indicator buttons. This release includes a patch which resolves this issue and allows users to navigate between pages using various UI elements.
+ </para>
+ <para>
+ Further details can be found in <ulink type="http" url="https://issues.jboss.org/browse/GTNPORTAL-1356"></ulink>
+ </para>
+
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-598 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-733 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-598" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></term>
<listitem>
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- Security vulnerabilies arising from the execution of XSS javascript entered into various portal form fields have been eradicated in this release.
- </para>
- <para>
- The resolution to this issue also resolves the following related JIRA issues:
- <simplelist>
- <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-847"></ulink></member>
- <member><ulink type="http" url="https://issues.jboss.org/browse/JBEPP-997"></ulink></member>
- </simplelist>
- </para>
- </warning>
-
+
+
+ <para>
+ A bug cause the JBoss Enterprise Portal Platform upload service to not work properly with Internet Explorer 7. As a result, any application using the upload service (such as Site Publisher) would not behave correctly with this web browser unless a name was provided. The bug has been fixed and the upload service now works as expected in all browsers (including IE7).
+ </para>
+
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-723 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-768 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-723" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-768" /></term>
<listitem>
-
+
+
<para>
- A bug in the <parameter>UIUserInGroup.setValues()</parameter> code caused previous versions of EPP to throw an error when users attempted to navigate to a new page withing the Group management view of the Organization portlet by any method other than the page indicator buttons. This release includes a patch which resolves this issue and allows users to navigate between pages using various UI elements.
+ An issue with the FileUpload demo not populating file information fields has been corrected with an upgrade to the Portlet Bridge component.
</para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-771 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-771" /></term>
+ <listitem>
+
+
<para>
- Further details can be found in <ulink type="http" url="https://issues.jboss.org/browse/GTNPORTAL-1356"></ulink>.
+ Prior to this release, CAS ticket validation failed when the JBoss Enterprise Portal Platform instance was set up with SSL. This has been fixed with an upgrade to the SSO component. CAS ticket validation now works as expected with http and https addresses.
</para>
-
+
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-733 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-772 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-772" /></term>
<listitem>
-
+
+
<para>
- A bug cause the JBoss Enterprise Portal Platform upload service to not work properly with Internet Explorer 7. As a result, any application using the upload service (such as Site Publisher) would not behave correctly with this web browser unless a name was provided. The bug has been fixed and the upload service now works as expected in all browsers (including IE7).
+ In this release of JBoss Enterprise Portal Platform, JndiMultiplexedJBossCacheRegionFactory is used for IDM second level caching. This makes it easier to switch to TCP.
</para>
-
+
</listitem>
</varlistentry>
@@ -109,11 +129,12 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-773" /></term>
<listitem>
-
+
+
<para>
- A bug prevented the 'Preferences' tab from appearing in some portlets. The tab would only appear in portlets that were customized during the first deployment through the portal.xml descriptor. Non-customized portlets would not show a 'Preferences' tab. The <filename>UIFormInputSet.java</filename> and <filename>UIPortletForm.java</filename> files have been patched to fix the issue and now the tab now appears in all portlets that have configurable preferences.
+ A bug prevented the 'Preferences' tab from appearing in some portlets. The tab would only appear in portlets that were customized during the first deployment through the portal.xml descriptor. Non-customized portlets would not show a 'Preferences' tab. The UIFormInputSet.java and UIPortletForm.java files have been patched to fix the issue and now the tab now appears in all portlets that have configurable preferences.
</para>
-
+
</listitem>
</varlistentry>
@@ -121,11 +142,12 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-780" /></term>
<listitem>
-
+
+
<para>
- The two JBoss Cache instances created by PicketLink were calling on the same configuration file in <filename>idm-configuration.xml</filename> and, as a result, were using the same cluster names. This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Separate configuration files were added to the distribution package and the Portal configuration was customized to call on the different files. JBoss Cache instances can now run simultaneously without conflict.
+ The two JBoss Cache instances created by PicketLink were calling on the same configuration file in idm-configuration.xml and, as a result, were using the same cluster names. This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Separate configuration files were added to the distribution package and the Portal configuration was customized to call on the different files. JBoss Cache instances can now run simultaneously without conflict.
</para>
-
+
</listitem>
</varlistentry>
@@ -133,11 +155,12 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-782" /></term>
<listitem>
-
+
+
<para>
- It was found that separate instances of epp 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster. This behavior has been resolved with new cluster configuration.
+ It was found that separate instances of JBoss Enterprise Portal Platform 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster. This behavior has been resolved with new cluster configuration.
</para>
-
+
</listitem>
</varlistentry>
@@ -145,11 +168,12 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-786" /></term>
<listitem>
-
+
+
<para>
- An error in the XML definition in the <filename>gatein_objects_1_0</filename> file was found to cause errors in Eclipse environments when using the default <filename>pages.xml</filename> or <filename>navigation.xml</filename> files. This was because the file did not include '<parameter>VISIBLE</parameter>' in the allowed values of the '<literal>visibility</literal>' element. This error has been corrected.
+ An error in the XML definition in the gatein_objects_1_0 file was found to cause errors in Eclipse environments when using the default pages.xml or navigation.xml files. This was because the file did not include 'VISIBLE' in the allowed values of the 'visibility' element. This error has been corrected.
</para>
-
+
</listitem>
</varlistentry>
@@ -157,14 +181,13 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-788" /></term>
<listitem>
-
+
+
<para>
- In previous versions of JBoss Enterprise Portal Platform, WSRP strict mode was not properly restored when the product was started. This has now been resolved.
+ Custom WSRP RegistrationPolicy implementations were not properly handled in previous versions of JBoss Enterprise Portal Platform.
+This caused an exception when the product was started. This issue has been resolved.
</para>
- <para>
- <remark>Possibly the same issue as JBEPP-857. Awaiting feedback from Chris Laprun.</remark>
- </para>
-
+
</listitem>
</varlistentry>
@@ -172,11 +195,25 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-794" /></term>
<listitem>
+
+
+ <para>
+ When adding resources (js, css, etc) to the Head of the HTML response with the doHeaders method a bug was encountered which caused those resources to be added twice. A patch has been applied to fix the bug and new resources are now only linked once.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-813 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-813" /></term>
+ <listitem>
+
+
<para>
- When adding resources (js, css, etc) to the Head of the HTML response with the <literal>doHeaders</literal> method a bug was encountered which caused those resources to be added twice. A patch has been applied to fix the bug and new resources are now only linked once.
+ An issue with navigational elements not being correctly translated into languages with a country variant has been resolved in this release. Navigation elements are now translated correctly.
</para>
-
+
</listitem>
</varlistentry>
@@ -184,11 +221,25 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-848" /></term>
<listitem>
+
+
+ <para>
+ A bug in data caching prevented some changes to Portal navigation from reloading in real time. When changing a group navigation priority, the reordering of the groups was only happening after a log-out. The UIPageNavigationForm.java has been patched to correct this and navigation changes now update immediately, without the user needing to log-out.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-856 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-856" /></term>
+ <listitem>
+
+
<para>
- A bug in data caching prevented some changes to Portal navigation from reloading in real time. When changing a group navigation priority, the reordering of the groups was only happening after a log-out. The <filename>UIPageNavigationForm.java</filename> has been patched to correct this and navigation changes now update immediately, without the user needing to log-out.
+ Problems encountered when trying to run various gadgets (including the RSS Reader) in a portal instance using secure https mode has been resolved in this release. All gadgets should now render and behave as expect in both http and https modes.
</para>
-
+
</listitem>
</varlistentry>
@@ -196,26 +247,64 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-857" /></term>
<listitem>
+
+
+ <para>
+ WSRP Strict mode was previously set only via listeners, which were not triggered at start up since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at start up.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-873 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-873" /></term>
+ <listitem>
+
+
<para>
- WSRP Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at startup.
- </para>
- <para>
- <remark>Possibly the same issue as JBEPP-788. Awaiting feedback from Chris Laprun.</remark>
+ Previous versions of JBoss Enterprise Portal Platform encountered problems when attempting to access files though the WebDAV interface if the file name included special characters. An upstream patch ensures characters are escaped correctly and resolves the issue.
</para>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-883 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-883" /></term>
+ <listitem>
+
+
+ <para>
+ Some mistranslations in webui_ja.properties have been corrected in this release of JBoss Enterprise Portal Platform.
+ </para>
+
</listitem>
</varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-887 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-887" /></term>
+ <listitem>
+
+
+ <para>
+ A conflict between the javax.portlet.faces.extension.resetModeViewId the portlet.xml configuration file and the error page specified by the error-page tag in web.xml has been resolved in an upgrade to the JBoss Portlet Bridge component.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
<!-- https://issues.jboss.org/browse/JBEPP-890 -->
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-890" /></term>
<listitem>
-
+
+
<para>
- Exceptions thrown by the <literal>handleFaceletNotFound</literal> method (when a facelet file was not found) were being obscured by <literal>FaceletViewHandler</literal> as the response object was not a subtype of <literal>HttpServletResponse</literal> (it is a instance of PortletResponse). <filename>FaceletPortletViewHandler.java</filename> has been updated to handle instances of both <literal>HttpServletResponse</literal> and <literal>PortletResponse</literal> response objects.
+ Exceptions thrown by the handleFaceletNotFound method (when a facelet file was not found) were being obscured by FaceletViewHandler as the response object was not a subtype of HttpServletResponse (it is a instance of PortletResponse). FaceletPortletViewHandler.java has been updated to handle instances of both HttpServletResponse and PortletResponse response objects.
</para>
-
+
</listitem>
</varlistentry>
@@ -223,11 +312,12 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-896" /></term>
<listitem>
-
+
+
<para>
- The Single Sign On (SSO) <literal>AbstractLogoutFilter</literal> in JBoss Enterprise Portal Platform would read request parameters before setting the character encoding. When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to the <literal>AbstractLogoutFilter</literal> code) resolves this issue and Non-UTF-8 characters are now specified correctly.
+ The Single Sign On (SSO) AbstractLogoutFilter in JBoss Enterprise Portal Platform would read request parameters before setting the character encoding. When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. An upgrade of the SSO component to version 1.0.2-EPP-GA (which includes a patch to the AbstractLogoutFilter code) resolves this issue and Non-UTF-8 characters are now specified correctly.
</para>
-
+
</listitem>
</varlistentry>
@@ -235,11 +325,12 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-902" /></term>
<listitem>
-
+
+
<para>
In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the Out Of Memory error is no longer encountered.
</para>
-
+
</listitem>
</varlistentry>
@@ -247,16 +338,46 @@
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-904" /></term>
<listitem>
+
+
+ <para>
+ JBoss Enterprise Portal Platform doesn't set content-type on css-files added via gatein-resources.xml. This causes Internet Explorer 9 to ignore these css-files due to new security policy (a console message states: SEC7113: CSS was ignored due to mime type mismatch). The ResourceRequestFilter.java file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-966 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-966" /></term>
+ <listitem>
+
+
<para>
- JBoss Enterprise Portal Platform doesn't set content-type on css-files added via <filename>gatein-resources.xml</filename>. This causes Internet Explorer 9 to ignore these css-files due to new security policy and output a console message:
+ In previous versions of JBoss Enterprise Portal Platform, the ErrorLoginServlet did not return the HTTP header content-type. This could be problematic when running the portal instance behind Apache loadbalancer. An upstream patch has been incorporated in this release to address the issue.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-987 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-987" /></term>
+ <listitem>
+
+
+ <para>
+ The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-&lt;version&gt;.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/.
</para>
-<screen>SEC7113: CSS was ignored due to mime type mismatch
-</screen>
<para>
- The ResourceRequestFilter.java file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected.
+ This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the JCR_CONFIG table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database.
</para>
-
+ <note>
+ <title>JCR_CONFIG Prefixes:</title>
+ <para>
+ After this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml).
+ </para>
+ </note>
</listitem>
</varlistentry>
13 years, 4 months
- 1
- 0