JBoss Portal SVN: r7647 - trunk/wsrp/src/main/org/jboss/portal/wsrp.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2007-06-29 09:46:03 -0400 (Fri, 29 Jun 2007)
New Revision: 7647
Modified:
trunk/wsrp/src/main/org/jboss/portal/wsrp/WSRPRewritingConstants.java
Log:
Fix encoding issue.
Modified: trunk/wsrp/src/main/org/jboss/portal/wsrp/WSRPRewritingConstants.java
===================================================================
--- trunk/wsrp/src/main/org/jboss/portal/wsrp/WSRPRewritingConstants.java 2007-06-29 12:26:35 UTC (rev 7646)
+++ trunk/wsrp/src/main/org/jboss/portal/wsrp/WSRPRewritingConstants.java 2007-06-29 13:46:03 UTC (rev 7647)
@@ -37,7 +37,7 @@
/**
* 10.2.1 <p>All portlet URLs (i.e. those the Consumer needs to rewrite) are demarcated in the markup by a token
- * (wsrp_rewrite) both at the start (with a �?� appended to clearly delimit the start of the name/value pairs).</p>
+ * (wsrp_rewrite) both at the start (with a '?' appended to clearly delimit the start of the name/value pairs).</p>
*/
public static final String BEGIN_WSRP_REWRITE = WSRP_REWRITE + "?";
@@ -45,7 +45,7 @@
/**
* 10.2.1 <p>All portlet URLs (i.e. those the Consumer needs to rewrite) are demarcated in the markup by a token
- * (wsrp_rewrite) at the end (proceeded by a �/� to form the end token) of the URL declaration.</p>
+ * (wsrp_rewrite) at the end (proceeded by a '/' to form the end token) of the URL declaration.</p>
*/
public static final String END_WSRP_REWRITE = "/" + WSRP_REWRITE;
@@ -68,7 +68,7 @@
/**
* 10.2.1.1.2 wsrp-urlType = render <p>Activation of the URL will result in an invocation of getMarkup(). This
- * mechanism permits a Portlet�s markup to contain URLs, which do not involve changes to local state, to avoid the
+ * mechanism permits a Portlet's markup to contain URLs, which do not involve changes to local state, to avoid the
* overhead of two-step processing by directly invoking getMarkup(). The URL MAY specify a wsrp-navigationalState
* portlet URL parameter, whose value the Consumer MUST supply in the navigationalState field of the MarkupParams
* structure. If there is no such portlet URL parameter, the Consumer MUST NOT supply a value for this field.</p>
@@ -79,7 +79,7 @@
* 10.2.1.1.3 wsrp-urlType = resource <p>Activation of the URL will result in the Consumer acting as a gateway to the
* underlying resource, possibly in a cached manner, and returning it to the user-agent. The URL for the resource
* (including any query string parameters) is encoded as the value of the wsrp-url parameter. When a portlet URL
- * specifies �resource� for the wsrp-urlType portlet URL parameter, both the wsrp-url and wsrp-requiresRewrite
+ * specifies 'resource' for the wsrp-urlType portlet URL parameter, both the wsrp-url and wsrp-requiresRewrite
* portlet URL parameters MUST also be specified. If the Portlet needs to share data with the referenced resource, it
* can exploit the cookie support defined in section 10.4.</p>
*/
@@ -88,7 +88,7 @@
/**
* 10.2.1.1.3.1 wsrp-url <p>This parameter provides the actual URL to the resource. Note that this needs to be an
* absolute URL as the resource fetch will have no base for use in fetching a relative URL. Also note that since this
- * resource URL will appear as a parameter value, it has to be strictly encoded (i.e. �&�, �=�, �/�, and �?� need to
+ * resource URL will appear as a parameter value, it has to be strictly encoded (i.e. '&', '=', '/', and '?' need to
* be url-escaped) so that special URL characters do not invalidate the processing of the enclosing URL. Consumers
* are encouraged to use the same communication style (e.g. HTTP Get or Post) for retrieving the resource as was used
* in requesting the resource by the user-agent.</p>
@@ -99,11 +99,11 @@
* 10.2.1.1.3.2 wsrp-requiresRewrite <p>This boolean informs the Consumer that the resource needs to be parsed for
* URL rewriting. Normally this means that there are names that will be cross-referenced between the markup and this
* resource (e.g. JavaScript references). Note that this means the Consumer needs to deal with rewriting unique
- * �namespaced� names in a set of documents, rather than treating each document individually. Processing such
- * resources in a manner that allows caching of the resulting resource by the End-User�s user-agent can improve the
+ * 'namespaced' names in a set of documents, rather than treating each document individually. Processing such
+ * resources in a manner that allows caching of the resulting resource by the End-User's user-agent can improve the
* performance of the aggregated page for the End-User. In particular, Consumers can process namespace rewriting by
* using a prefix that is unique to the user/Portlet pair provided any such prefix is held constant for the duration
- * of use within the user�s session with the Consumer of any one Portlet.</p>
+ * of use within the user's session with the Consumer of any one Portlet.</p>
*/
public static final String RESOURCE_REQUIRES_REWRITE = "wsrp-requiresRewrite";
@@ -125,8 +125,8 @@
* 10.2.1.4 wsrp-mode <p>Activating this URL includes a request to change the mode parameter in MarkupParams into the
* mode specified as the value for this portlet URL parameter. The value for wsrp-mode MUST be one of the modes
* detailed in section 6.8 or a custom mode the Consumer specified as supported during registration. The wsrp-mode
- * portlet URL parameter MAY be used whenever the wsrp-urlType portlet URL parameter has a value of �blockingAction�
- * or �render�.</p>
+ * portlet URL parameter MAY be used whenever the wsrp-urlType portlet URL parameter has a value of 'blockingAction'
+ * or 'render'.</p>
*/
public static final String MODE = "wsrp-mode";
@@ -135,7 +135,7 @@
* MarkupParams into the window state specified as the value for this portlet URL parameter. The value for wsrp-
* windowState MUST be one of the values detailed in section 6.9 or a custom window state the Consumer specified as
* supported during registration. The wsrp-windowState portlet URL parameter MAY be used whenever the wsrp-urlType
- * portlet URL parameter has a value of �blockingAction� or �render�.</p>
+ * portlet URL parameter has a value of 'blockingAction' or 'render'.</p>
*/
public static final String WINDOW_STATE = "wsrp-windowState";
@@ -148,14 +148,14 @@
/**
* 10.2.1.7 wsrp-secureURL <p>The value for the wsrp-secureURL is a boolean indicating whether the resulting URL MUST
* involve secure communication between the client and Consumer, as well as between the Consumer and Producer. The
- * default value of this boolean is �false�. Note that the Consumer�s aggregated page MUST be secure if any of the
+ * default value of this boolean is 'false'. Note that the Consumer's aggregated page MUST be secure if any of the
* Portlets whose content is being displayed on the page have indicated the need for secure communication for their
* current markup.</p>
*/
public static final String SECURE_URL = "wsrp-secureURL";
/**
- * 10.3.1 Consumer Rewriting (Namespace encoding) <p>The Portlet can prefix the token with �wsrp_rewrite_�. The
+ * 10.3.1 Consumer Rewriting (Namespace encoding) <p>The Portlet can prefix the token with 'wsrp_rewrite_'. The
* Consumer will locate such markers and MUST replace them with a prefix that is unique to this instance of this
* portlet on the page. This prefix has been chosen such that the Consumer is able to do a single parse of the markup
* to both locate such markers and the URL rewrite expressions described in section 10.2.1. In addition, this prefix
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7645 - in docs: trunk/quickstartuser/en and 1 other directory.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2007-06-29 08:19:49 -0400 (Fri, 29 Jun 2007)
New Revision: 7645
Modified:
docs/tags/JBoss_Portal_2_6_0/quickstartuser/en/master.xml
docs/trunk/quickstartuser/en/master.xml
Log:
For consistency sake
Modified: docs/tags/JBoss_Portal_2_6_0/quickstartuser/en/master.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/quickstartuser/en/master.xml 2007-06-29 12:18:24 UTC (rev 7644)
+++ docs/tags/JBoss_Portal_2_6_0/quickstartuser/en/master.xml 2007-06-29 12:19:49 UTC (rev 7645)
@@ -11,14 +11,10 @@
]>
<book lang="en">
<bookinfo>
- <title>JBoss Portal 2.6</title>
-
+ <title>JBoss Portal 2.6.0-GA</title>
<subtitle>Quickstart User Guide</subtitle>
+ <releaseinfo>Release 2.6.0-GA "Ninja"</releaseinfo>
- <releaseinfo>Release 2.6 "Ninja"</releaseinfo>
-
- <releaseinfo>June 2007</releaseinfo>
-
<author>
<firstname>Kevin</firstname>
Modified: docs/trunk/quickstartuser/en/master.xml
===================================================================
--- docs/trunk/quickstartuser/en/master.xml 2007-06-29 12:18:24 UTC (rev 7644)
+++ docs/trunk/quickstartuser/en/master.xml 2007-06-29 12:19:49 UTC (rev 7645)
@@ -11,14 +11,10 @@
]>
<book lang="en">
<bookinfo>
- <title>JBoss Portal 2.6</title>
-
+ <title>JBoss Portal 2.6.0-GA</title>
<subtitle>Quickstart User Guide</subtitle>
+ <releaseinfo>Release 2.6.0-GA "Ninja"</releaseinfo>
- <releaseinfo>Release 2.6 "Ninja"</releaseinfo>
-
- <releaseinfo>June 2007</releaseinfo>
-
<author>
<firstname>Kevin</firstname>
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7644 - trunk/build/misc.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2007-06-29 08:18:24 -0400 (Fri, 29 Jun 2007)
New Revision: 7644
Modified:
trunk/build/misc/codeguide.html
Log:
update coding conventions with appropriate headers
Modified: trunk/build/misc/codeguide.html
===================================================================
--- trunk/build/misc/codeguide.html 2007-06-29 12:06:21 UTC (rev 7643)
+++ trunk/build/misc/codeguide.html 2007-06-29 12:18:24 UTC (rev 7644)
@@ -23,12 +23,28 @@
<h3>A class that conforms to JBoss coding guidelines</h3>
<pre>
-/*
- * JBoss, the OpenSource J2EE webOS
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2006, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
package x;
// <span class="important">Explicit imports</span>
@@ -114,4 +130,4 @@
}
</pre>
</body>
-</html>
\ No newline at end of file
+</html>
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7643 - in docs: trunk/userGuide/en/images/management and 1 other directory.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2007-06-29 08:06:21 -0400 (Fri, 29 Jun 2007)
New Revision: 7643
Added:
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/tree.gif
docs/trunk/userGuide/en/images/management/tree.gif
Log:
Missing tree.gif
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/tree.gif
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/tree.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/trunk/userGuide/en/images/management/tree.gif
===================================================================
(Binary files differ)
Property changes on: docs/trunk/userGuide/en/images/management/tree.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7642 - in docs: tags/JBoss_Portal_2_6_0/referenceGuide/en/images and 8 other directories.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2007-06-29 07:59:43 -0400 (Fri, 29 Jun 2007)
New Revision: 7642
Added:
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/adminportal.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignportlets.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_configure.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_copy_to.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_deletepage.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/greetings.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/logged.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newspage.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet_edit.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/tabs.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_create.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_loggedin.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config1.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config4.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config5.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_after.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_layout.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_rename.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_properties.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_security.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_theme.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/google_window.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/instances.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_cms1.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_cms2.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_content.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_final.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google1.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google2.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google3.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_instance.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_region.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portals.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portals_properties.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portlets.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/wizard.png
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/setup/default_ss.png
docs/trunk/userGuide/en/images/intro/weather_config4.png
docs/trunk/userGuide/en/images/intro/weather_config5.png
Removed:
docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/images/descriptors/
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/adminpage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard.jpg
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_add.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignportlets.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignthemes.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_configure.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_createpage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_dnd.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_dnd.jpg
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_selectpage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/greetings_portlet.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/login.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/login.jpg
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/nav2.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newspage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet_edit.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_create.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_loggedin.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config1.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config4.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config5.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/createinstance.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/createpage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/createwindow.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/manage_page.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/management_1.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/manageportal.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/managewindow.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portletpreferences.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/securepage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/secureportal.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/secureportlet.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/themepage.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/themeportal.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/themewindow.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/tree.gif
docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/windowtheme.gif
docs/trunk/userGuide/en/images/intro/weather_config4.gif
docs/trunk/userGuide/en/images/intro/weather_config5.gif
Modified:
docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/master.xml
docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/security.xml
docs/tags/JBoss_Portal_2_6_0/userGuide/en/master.xml
docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/dynamicity.xml
docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/featurelist.xml
docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/intro.xml
docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/overview.xml
docs/trunk/userGuide/en/modules/intro.xml
Log:
Sync trunk with 2.6.0.GA
Modified: docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/master.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/master.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/master.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -31,9 +31,9 @@
]>
<book lang="en">
<bookinfo>
- <title>JBoss Portal 2.6</title>
+ <title>JBoss Portal 2.6.0-GA</title>
<subtitle>Reference Guide</subtitle>
- <releaseinfo>Release 2.6 "Ninja"</releaseinfo>
+ <releaseinfo>Release 2.6.0-GA "Ninja"</releaseinfo>
<releaseinfo>June 2007</releaseinfo>
<author>
<firstname>Thomas</firstname>
@@ -55,6 +55,11 @@
<surname>Dawidowicz</surname>
<email>boleslaw dot dawidowicz at redhat dot com</email>
</author>
+ <author>
+ <firstname>Chris</firstname>
+ <surname>Laprun</surname>
+ <email>chris.laprun(a)jboss.com</email>
+ </author>
</bookinfo>
<toc/>
<!-- Portal overview - marketing stuff --> &overview;
Modified: docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/security.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/security.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/security.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -336,7 +336,7 @@
about it.</listitem>
<listitem><emphasis>/auth/*</emphasis> : the authenticated access, requires the user to be authenticated
to be used.</listitem>
- <listitem>/authsec/*<emphasis></emphasis> : combine thet two previous options into a single one.</listitem>
+ <listitem><emphasis>/authsec/*</emphasis> : combine thet two previous options into a single one.</listitem>
</itemizedlist>
Usually ones should not care much about those mappings as the portal will by itself switch to the most appropriate mapping.
</para>
@@ -388,8 +388,6 @@
</para>
</sect2>
<sect2>
- </sect2>
- <sect2>
<title>Making a programmatic security check</title>
<para>Making a security check is an easy thing as it consists in created a permission of the appropriate type and
make a check against the <emphasis>org.jboss.portal.spi.auth.PortalAuthorizationManager</emphasis> service. That
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/adminpage.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/adminportal.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/adminportal.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard.jpg
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_add.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignportlets.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignportlets.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignportlets.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_assignthemes.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_configure.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_configure.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_configure.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_copy_to.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_copy_to.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_createpage.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_deletepage.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_deletepage.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_dnd.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_dnd.jpg
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/dashboard_selectpage.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/greetings.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/greetings.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/greetings_portlet.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/logged.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/logged.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/login.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/login.jpg
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/nav2.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newspage.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newspage.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newspage.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet_edit.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet_edit.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/newsportlet_edit.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/tabs.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/tabs.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_create.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_create.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_create.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_loggedin.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_loggedin.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/user_portlet_loggedin.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config1.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config1.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config4.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config4.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config5.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config5.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/intro/weather_config5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/createinstance.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/createpage.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/createwindow.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_after.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_after.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_layout.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_layout.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_rename.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_page_rename.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_properties.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_properties.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_security.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_security.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_theme.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/default_portal_theme.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/google_window.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/google_window.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/instances.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/instances.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_cms1.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_cms1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_cms2.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_cms2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_content.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_content.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_final.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_final.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google1.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google2.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google3.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_google3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_instance.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_instance.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_region.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/layout_region.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/manage_page.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/management_1.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/manageportal.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/managewindow.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portals.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portals.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portals_properties.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portals_properties.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portletpreferences.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portlets.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/portlets.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/securepage.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/secureportal.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/secureportlet.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/themepage.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/themeportal.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/themewindow.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/tree.gif
===================================================================
(Binary files differ)
Deleted: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/windowtheme.gif
===================================================================
(Binary files differ)
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/wizard.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/management/wizard.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/setup/default_ss.png
===================================================================
(Binary files differ)
Property changes on: docs/tags/JBoss_Portal_2_6_0/userGuide/en/images/setup/default_ss.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/master.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/master.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/master.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -13,9 +13,9 @@
]>
<book lang="en">
<bookinfo>
- <title>JBoss Portal 2.6</title>
+ <title>JBoss Portal 2.6.0-GA</title>
<subtitle>User Guide</subtitle>
- <releaseinfo>Release 2.6 "Ninja"</releaseinfo>
+ <releaseinfo>Release 2.6.0-GA "Ninja"</releaseinfo>
<releaseinfo>June 2007</releaseinfo>
<author>
<firstname>Roy</firstname>
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/dynamicity.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/dynamicity.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/dynamicity.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -2,9 +2,9 @@
<chapter id="dynamicity">
<chapterinfo>
<author>
- <firstname>Roy</firstname>
- <surname>Russo</surname>
- <email>roy(a)jboss.org</email>
+ <firstname>Chris</firstname>
+ <surname>Laprun</surname>
+ <email>chris.laprun(a)jboss.com</email>
</author>
</chapterinfo>
<title>Administration - Portal Object Management (Dynamicity)</title>
@@ -36,327 +36,450 @@
user session. In order to see the changes on the affected pages, please log out and log back in.
</note>
</sect1>
- <sect1>
- <title>Actions</title>
- <para>Dynamicity allows an administrator to manage the entire portal deployment from within
- a portlet. Some of the many tasks available to administrators are:
+ <sect1 id="management_portlet">
+ <title>Management Portlet</title>
+ <note>For the remainder of this chapter, the term <emphasis role="bold">object</emphasis> will be used to mean
+ Portal, Page, Portlet, or Window indifferently.
+ </note>
+ <para>
+ The management portlet provides a two-part interface: tabs, at the top, corresponding to the different sections
+ that can be managed; and the main area under it, displaying the current information for the selected
+ tab.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/intro/adminportal.png" format="png" align="center" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>
+ The tabs are:
<itemizedlist>
- <listitem>
- <xref linkend="manageportal"/>
- <itemizedlist>
- <listitem>
- <xref linkend="secureportal"/>
- </listitem>
- <listitem>
- <xref linkend="themeportal"/>
- </listitem>
- </itemizedlist>
+ <listitem><emphasis>Portal Objects</emphasis> gathering operations pertaining to managing portal objects
+ (portal instances, pages, windows and their respective configuration information). This is the most
+ complex part of the interface.</listitem>
+ <listitem><emphasis>Portlet Instances</emphasis> giving access to all the Portlet instances that have been
+ configured.</listitem>
+ <listitem><emphasis>Portlet Definitions</emphasis> giving access to the currently available portlet
+ providers as well as the Portlets that each provider publishes.</listitem>
+ <listitem><emphasis>Dashboards</emphasis> allowing administrators to configure how Dashboards should behave.
</listitem>
- <listitem>
- <xref linkend="managepages"/>
- <itemizedlist>
- <listitem>
- <xref linkend="createportletwindows"/>
- </listitem>
- <listitem>
- <xref linkend="editportletwindow"/>
- </listitem>
- <listitem>
- <xref linkend="themewindows"/>
- </listitem>
- <listitem>
- <xref linkend="securepages"/>
- </listitem>
- <listitem>
- <xref linkend="pagethemelayout"/>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <xref linkend="manageportletinstance"/>
- <itemizedlist>
- <listitem>
- <xref linkend="createportletinstance"/>
- </listitem>
- <listitem>
- <xref linkend="portletinstanceprefs"/>
- </listitem>
- <listitem>
- <xref linkend="securinginstances"/>
- </listitem>
- </itemizedlist>
- </listitem>
</itemizedlist>
+ We will look at each of these tabs and their functionality in the following sections.
</para>
- <note>For the remainder of this chapter, the term
- <emphasis role="bold">object</emphasis>
- will be used to mean any Portal, Page, Portlet, or Window.
- </note>
- <sect2 id="manageportal">
- <title>Managing portal instances</title>
- <para>Administrators may manage the portal, pages, subpages, and windows at any time, by
- clicking on the "Portal" tab at the top of the Management Portlet. The components
- currently deployed in the portal container are displayed in a tree-structure for
- ease-of-navigation and modification.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/manageportal.gif" format="gif" align="center" valign="middle"/>
- </imageobject>
- </mediaobject>
- Expanding the tree structure will reveal all pages and portlet windows deployed in a particular portal
- instance.
- </para>
- <sect3 id="secureportal">
- <title>Securing portal instances</title>
- <para>
+ <sect2 id="admin_portal_objects">
+ <title>Managing Portal Objects</title>
+ <sect3 id="portals_operations">
+ <title>Portals operations</title>
+
<mediaobject>
<imageobject>
- <imagedata fileref="images/management/secureportal.gif" format="gif" align="center"
- valign="middle"/>
+ <imagedata fileref="images/management/portals.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- Selecting the
- <emphasis>Security</emphasis>
- option, allows an administrator to
- secure the portal instance. On this screen, you can select and unselect portal-wide
- security settings for a given role. Security settings are defined as follows:
- <itemizedlist>
- <listitem>
- <emphasis role="bold">view</emphasis>
- Users can view the object.
- </listitem>
- <listitem>
- <emphasis role="bold">viewrecursive</emphasis>
- Users can view the object and child objects.
- </listitem>
- <listitem>
- <emphasis role="bold">personalize</emphasis>
- Users are able to view AND personalize the object.
- </listitem>
- <listitem>
- <emphasis role="bold">personalizerecursive</emphasis>
- Users are able to view AND personalize the object AND its child objects.
- </listitem>
- </itemizedlist>
- </para>
- </sect3>
- <sect3 id="themeportal">
- <title>Modifying the portal Theme/Layout</title>
+
+ <para>
+ The <literal>Portal Objects</literal> brings the administrator to a page showing the list of the
+ available portal instances defined for this Portal server. Several points are of note. First, a
+ navigation indicator or "breadcrumbs" is located right beneath the tabs. This provides context as to
+ where in the hierarchy of portal objects the current screen is located as some of the screens can be
+ found at several levels of the hierarchy. If you are lost, take a look at the breadcrumbs for context!
+ When you first click on the <literal>Portal Objects</literal> tab, the context is the list of portals
+ as shown in the picture above.
+ </para>
+
+ <para>
+ A link to access server-wide portal properties is located right beneath the breadcrumbs. This allows
+ the administrator to set server-wide property and configure how errors should be handled:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/portals_properties.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Please refer to the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/errorhandling...">Error
+ handling chapter</ulink> of the Reference Guide for more information on this point.
+ </para>
+
+ <para>
+ A form allowing administrator to create new portal instances is located beneath the
+ <literal>Properties</literal> link. Enter the name of the new portal (which, of course, should be
+ different from any of the already existing one) and click on <literal>Add portal</literal> and the
+ portal instances list will be refreshed to display the newly created portal instance.
+ </para>
+
+ <para>
+ The last element of the top level of the <literal>Portal Objects</literal> tab is a table listing
+ all the available portal instances along with possible actions on them. Clicking on the portal name
+ will display a screen showing the information for this given portal instance, thus drilling down the
+ hierarchy of available portal objects.
+ </para>
+
+ <para>
+ In the next sections we will demonstrate the functionality of the management portlet by drilling
+ progressively further down this hiearchy to look at the default portal, one of its pages, show
+ how to configure content on a page and finally, look at a specific window information.
+ </para>
+ </sect3>
+
+
+ <sect3 id="portal_instance_configuration">
+ <title>Looking at a portal instance information</title>
+
+ <para>
+ If you click on the <literal>default</literal> portal in the list of available portal instances on the
+ top-level <literal>Portal Objects</literal> page, you'll be taken to a page showing the information
+ for the portal instance named "default", as shown below:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_portal.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Note the breadcrumbs at the top of the screen indicating where in the hierachy you currently are.
+ In this case, we are looking at the default portal.
+ </para>
+
+ <para>
+ Links to more information and operations that
+ affect this portal instance are located beneath the breadcrumbs. We will look at them in turn later.
+ We won't look at the <literal>Destroy</literal> operation, which as its name implies, allows an
+ administrator to destroy the current portal instance (after a confirmation screen, as the operation is
+ <emphasis role="bold">NOT</emphasis> undoable). Note that these links mirror the links that were
+ available in the portal instances list on the top level page.
+ </para>
+
+ <para>
+ It is possible to create new pages using the page creation form located under the portal-wide
+ operation links. Enter the new page name and click on <literal>Add</literal> and the new page will
+ appear in the pages list, ready to be configured.
+ </para>
+
+ <para>
+ It is also possible to designate one of the portal page as the default page that users are directed
+ to when they first access the portal instance. This is done by selecting the page via the page
+ selection drop-down menu and then click on <literal>Update</literal>.
+ </para>
+
+ <para>
+ Finally, a table displaying the list of available pages for this portal instance is located at the
+ bottom of this screen. The first column shows the page name, which you can click to drill down the
+ hierachy and display the information specific to that particular page. The second column, on the other
+ hand, provides a list of action links on the associated page. These links
+ will be also appearing on individual page screens, as we shall see, just like portal action links
+ appearing in the portal instances list also appeared on individual portal pages.
+ </para>
+
+ <para>
+ Let's now look at the default portal's <literal>Security</literal> information screen. This can be
+ accessed by clicking the <literal>Security</literal> action link on the portal page. Here, an
+ administrator can configure the default policy for security on objects for this portal instance:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_portal_security.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Please refer to the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/security.html">Security</ulink>
+ chapter of the Reference Guide for more information about how to secure portal objects.
+ </para>
+
+ <para>
+ The <literal>Properties</literal> action link displays the currently configured properties for this
+ portal instance and allows you to modify them, as well as configure the error handling strategy:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_portal_properties.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ <para>
+ The <literal>Theme</literal> action link displays a screen where the administrator can configure theme,
+ layout and render set for this portal instance:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_portal_theme.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Please refer to the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/themeandlayou...">Layouts
+ and Themes</ulink> chapter of the Reference Guide for more information about themes and layouts.
+ </para>
+
+ <para>
+ Now that we have looked at portal level information, let's drill down the hierachy again and look at
+ a page, more precisely the <literal>default</literal> page, by clicking its name in the pages list.
+ </para>
+ </sect3>
+
+ <sect3 id="page_configuration">
+ <title>Looking at a page configuration</title>
+
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_page.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ The layout of this screen should start feeling familiar. The information for a page looks a lot like the
+ information for a portal instance. Note the breadcrumbs indicating that you are indeed looking at a
+ page. Again, we find the action links at the top of the page, mirroring the ones that were available
+ for each page in the pages list of the portal instance screen. Once again, you can configure the page's
+ security, theme and properties. You can also destroy it if so desired.
+ </para>
+
+ <para>
+ Similarly to other screens in the portal objects hierarchy, a page configuration screen also provides
+ a list of all windows for that page. This list contains two columns: the first one contains the
+ name of the window, while the second one provides a list of action links for that specific window.
+ As usual, clicking on a window name will display information about that window.
+ </para>
+
+ <para>
+ Just like a portal instance can contain several pages, a page can contain several subpages. As such
+ a page defines means to create subpages and set which subpage to display when a user is first directed
+ to the page. These operations work similarly to the same operations at the portal instance level.
+ </para>
+
+ <para>
+ You can also rename the page if desired:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_page_rename.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ <para>
+ Of specific interest, though, is the <literal>Page Layout</literal> link. This is where you need to
+ go to configure which portlet instance will be displayed in which window on which region on the page.
+ Let's take a look at this screen and how it works:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_page_layout.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+
+ This screen is structured in two parts, flowing from left to right, following the natural process
+ involved in displaying content on a page. First, you need to identify which content you want to
+ display: this is what the <literal>Content Definition</literal> section is for. Then, you need to
+ figure out where on the page should this content be displayed, hence the <literal>Page Layout</literal>
+ section.
+ </para>
+
+ <para>
+ Let's add a window named <literal>test</literal> displaying the content of the portlet instance
+ named <literal>NewsPortletInstance</literal> to the center region, beneath the already existing
+ <literal>CMSWindow</literal>.
+ First, we need to enter our new window name in the <literal>Window name</literal> field and select
+ the <literal>portlet</literal> content type from the drop down menu:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_content.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Once this is done, we can select the portlet instance by clicking its name in the instances list:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_instance.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Note that this displays some information about the portlet instance.
+ Finally, we can add our window to the center region of the page by clicking on <literal>Add</literal>
+ button located left to the windows list for the region:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_region.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Note that we could move the window up or down in the region by selecting it in the list and using the
+ button to the right of the list, or even destroy it if desired.
+ </para>
+
+ <para>
+ We can repeat this process to add content of different types. Let's add a window using a Google widget
+ displaying the IP address of the user. First, give a name to your window (we'll use "google" here)
+ and select <literal>widget/google</literal> from the content type drop-down menu:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_google1.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Note how the instances list is replaced by a list of Google widgets. The widget we want to use is
+ located in the <literal>Technology</literal> category, so select it from the category drop-down menu:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_google2.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Press <literal>Search Gadgets</literal> and the widget list will be refreshed. The widget we want is
+ <literal>MyIP</literal>:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_google3.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ You can now add the new window to the desired region.
+ </para>
+
+ <para>
+ Let's repeat this process again, this time with content from CMS. Enter a new window name (we'll
+ use "cms" here) and select <literal>cms</literal> from the content type drop-down menu:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_cms1.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Once again, the instances list was replaced by a directory listing showing the available content roots.
+ Click on <literal>default</literal> and select <literal>project.html</literal>:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_cms2.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ You can now add the window to the desired region.
+ </para>
+
+ <para>
+ We've added three new windows to the default page using different content types. We added a window
+ displaying the content of a portlet (displaying the content of an RSS feed in this case). Another one
+ displaying a Google widget and yet another one some CMS-issued content. We decided to remove the
+ existing <literal>CMSWindow</literal>, add the <literal>cms</literal> window below the
+ <literal>test</literal> one in the center region, while the window showing the Google widget was added
+ to the left region, below the existing content:
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/layout_final.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ If all went well, logging out of the Admin portal, you should see (IP address blurred to protect
+ the guilty ^_^):
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/default_page_after.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+
+ <para>
+ You can read more about
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/contentintegr...">Content
+ Integration</ulink> in the Reference Guide. More details on how to setup content roots in CMS are
+ available in <xref linkend="cmsadmin"/>.
+ </para>
+ </sect3>
+
+ <sect3 id="window_configuration">
+ <title>Looking at windows of a given page</title>
<para>
+ Window operations are similar to the same operations at other level of the hierachy of portal objects.
+ The only information displayed when a window name is clicked in the windows list of a portal page
+ information screen is information about the content, similar to the one that is displayed in the
+ page layout screen. Thus, for the <literal>google</literal> window that we created in the previous
+ section:
<mediaobject>
- <imageobject>
- <imagedata fileref="images/management/themeportal.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- Selecting the
- <emphasis>Theme</emphasis>
- option, allows an administrator to modify
- the look-and-feel for the chosen portal instance. An administrator is also able to choose a specific
- layout for a portal, as well as a theme.
+ <imageobject>
+ <imagedata fileref="images/management/google_window.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ Note, once again, the breadcrumbs... :)
</para>
</sect3>
</sect2>
- <sect2 id="manageportletinstance">
- <title>Managing portlets and portlet instances</title>
- <sect3 id="createportletinstance">
- <title>Creating portlet instances</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/createinstance.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <para>Clicking on the
- <emphasis>Portlet</emphasis>
- tab and then clicking on a specific
- portlet allows you to create a new instance of this portlet.
- </para>
- </sect3>
- <sect3 id="portletinstanceprefs">
- <title>Modifying portlet instance preferences</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/portletpreferences.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <para>Clicking on the
- <emphasis>Instance</emphasis>
- tab and selecting a portlet
- instance, displays a screen which allows an administrator to edit the portlet
- instance preferences.
- </para>
- </sect3>
- <sect3 id="securinginstances">
- <title>Securing portlets</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/secureportlet.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- Selecting the
- <emphasis>Security</emphasis>
- option, allows an administrator to
- secure the portlet instance. Security settings are defined as follows:
- <itemizedlist>
- <listitem>
- <emphasis role="bold">view</emphasis>
- Users can view the object.
- </listitem>
- <listitem>
- <emphasis role="bold">viewrecursive</emphasis>
- Users can view the object and child objects.
- </listitem>
- <listitem>
- <emphasis role="bold">personalize</emphasis>
- Users are able to view AND personalize the object.
- </listitem>
- <listitem>
- <emphasis role="bold">personalizerecursive</emphasis>
- Users are able to view AND personalize the object AND its child objects.
- </listitem>
- </itemizedlist>
- </para>
- <note>Depending on whether you are securing a portlet or an instance, keep in mind that
- instance security constraints take precedence over portlet security settings.</note>
- </sect3>
+ <sect2 id="admin_portlet_instances">
+ <title>Managing Portlet Instances</title>
+ <para>
+ The <literal>Portlet Instances</literal> tab brings the administrator to the list of instances created
+ in the running portal. On this page, the user can either modify the security constraints for the portlet
+ (to grant access only to certain roles), destoy an instance or override the portlet definition preferences
+ for a specific instance if there is any overridable preference.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/instances.png" format="png" align="center" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
</sect2>
- <sect2 id="managepages">
- <title>Managing Portal Pages</title>
+ <sect2 id="admin_portlet_definitions">
+ <title>Managing Portlet Definitions</title>
<para>
+ The <literal>Portlet Definitions</literal> tab brings the administrator to the list of portlet
+ definitions. The id represent the portlet definition identifier as used in the XML descriptor.
+ A more human readable name is following in the next column. For each portlet accessed through WSRP,
+ the <literal>remote</literal> checkbox is selected. A <literal>remotable</literal> checkbox is used to show which
+ portlet are exposed through WSRP to other consumers.
+ </para>
+ <para>
+ The <literal>Info</literal> action, will display the portlet definition title, description, supported languages
+ and keywords. The <literal>Preferences</literal> action is used to edit preferences at the portlet definition level
+ as explained in the JSR-168 specification.
<mediaobject>
<imageobject>
- <imagedata fileref="images/management/manageportal.gif" format="gif" align="center" valign="middle"/>
+ <imagedata fileref="images/management/portlets.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- Expanding the tree structure will reveal all pages deployed in a particular portal
- instance, that an administrator can then customize.
</para>
- <sect3 id="createpage">
- <title>Creating portal pages</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/createpage.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- By selecting a portal instance, and then selecting the
- <emphasis>Manage</emphasis>
- option, you can create a new page. Simply assign a name
- to a page and submit the form.
- </para>
- </sect3>
- <sect3 id="createportletwindows">
- <title>Creating portlet windows</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/createwindow.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <para>Selecting a portal page, allows you to
- <emphasis>Manage</emphasis>
- the order in
- which windows appear and the layout column in which they will appear. Additionally,
- you can name and assign portlet windows on the selected page, create subpages, or even delete the page.
- </para>
- </sect3>
- <sect3 id="editportletwindow">
- <title>Edit portlet windows</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/managewindow.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <para>Selecting a portlet window, allows you to
- <emphasis>Manage</emphasis>
- which portlet instance is assigned to it, and even delete/remove the window from the page.
- </para>
- </sect3>
- <sect3 id="themewindows">
- <title>Modifying the Window Theme/Layout</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/themewindow.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <para>Selecting a portal window under the
- <emphasis>Portal</emphasis>
- tab, and selecting
- the
- <emphasis>Theme</emphasis>
- option, allows an administrator to modify the
- look-and-feel for the chosen portal page.
- </para>
- <note>From this screen, an administrator can elect to set all values to
- <emphasis>emptyrenderer</emphasis>
- so the portlet window is displayed with no
- decorations and appears to be part of the layout.
- </note>
- </sect3>
- <sect3 id="securepages">
- <title>Securing portal pages</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/securepage.gif" format="gif" align="center" valign="middle"/>
- </imageobject>
- </mediaobject>
- Selecting the
- <emphasis>Security</emphasis>
- option, allows an administrator to
- secure the portal page. On this screen, you can select and unselect page security
- settings for a given role. Security settings are defined as follows:
- <itemizedlist>
- <listitem>
- <emphasis role="bold">view</emphasis>
- Users can view the object.
- </listitem>
- <listitem>
- <emphasis role="bold">viewrecursive</emphasis>
- Users can view the object and child objects.
- </listitem>
- <listitem>
- <emphasis role="bold">personalize</emphasis>
- Users are able to view AND personalize the object.
- </listitem>
- <listitem>
- <emphasis role="bold">personalizerecursive</emphasis>
- Users are able to view AND personalize the object AND its child objects.
- </listitem>
- </itemizedlist>
- </para>
- </sect3>
- <sect3 id="pagethemelayout">
- <title>Modifying the Page Theme/Layout</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/management/themepage.gif" format="gif" align="center" valign="middle"/>
- </imageobject>
- </mediaobject>
- Selecting the
- <emphasis>Theme</emphasis>
- option, allows an administrator to modify
- the look-and-feel for the chosen portal page.
- </para>
- </sect3>
+ <para>
+ Portlet definitions can be made available by different providers. You can select the provider you want to
+ browse by selecting it in the drop-down menu and clicking <literal>Change</literal>.
+ By default, two providers are available:
+ <itemizedlist>
+ <listitem>
+ <emphasis>local</emphasis>: this is Portal's portlet container. Any successfully deployed portlet will
+ appear in the list of available portlet definitions for this provider.
+ </listitem>
+ <listitem>
+ <emphasis>self</emphasis>: this is Portal's default WSRP consumer configured to consume portlets
+ published by Portal's own WSRP producer. This doesn't have much practical interest apart from allowing
+ a quick test of the WSRP functionality of Portal.
+ </listitem>
+ </itemizedlist>
+ More providers can be added to this list. In particular, any active, properly configured WSRP consumer will
+ also appear in the drop-down menu. Please refer to the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/wsrp.html#con...">Consuming
+ remote WSRP portlets in JBoss Portal</ulink> chapter of the Reference Guide for more information on this
+ topic.
+ </para>
</sect2>
+ <sect2 id="admin_dashboards">
+ <title>Managing Dashboards</title>
+ <para>
+ The <literal>Dashboards</literal> tab allows the administrator to configure parameters for all the user dashboards.
+ It also allows her to configure the error pages and theme properties as for the other portal objects.
+ </para>
+ </sect2>
+ <sect2 id="admin_wizard">
+ <title>Wizard mode</title>
+ <para>
+ The wizard mode is a fast and easy way to create a new window on a page backed by a portlet instance.
+ The user just needs to define which portlet definition to use, where should the instance be located
+ (portal / page / location on the page) and the wizard will automatically create a new instance of
+ the portlet, create a window for it and add that window to the specified region on the page
+ defined by the user.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/management/wizard.png" format="png" align="center" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </sect2>
</sect1>
</chapter>
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/featurelist.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/featurelist.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/featurelist.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -65,7 +65,9 @@
<emphasis role="bold">Java Management Extension (JMX) 1.2</emphasis>
</listitem>
<listitem>
- <emphasis role="bold">Web Services for Remote Portlets (WSRP) 1.0 Base Level </emphasis>
+ <emphasis role="bold">Web Services for Remote Portlets (WSRP) 1.0</emphasis>
+ See <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/wsrp.html#wsr...">WSRP
+ support in Portal</ulink> for more details.
</listitem>
<listitem>
<emphasis role="bold">Full J2EE 1.4 compliance when used with JBoss AS</emphasis>
@@ -82,16 +84,12 @@
instances running inside of one Portal container.
</listitem>
<listitem>
- <emphasis role="bold">
- <trademark class="trade">IPC</trademark>
- </emphasis>
+ <emphasis role="bold">IPC</emphasis>
Inter-Portlet Communication API enables portlets to create links to other
objects such as a page, portal or window .
</listitem>
<listitem>
- <emphasis role="bold">
- <trademark class="trade">Dynamicity</trademark>
- </emphasis>
+ <emphasis role="bold">Dynamicity</emphasis>
The ability for administrators and users to create and destroy objects such as
portlets, pages, portals, themes, and layouts at runtime.
</listitem>
@@ -115,31 +113,8 @@
Portlets utilizing Struts,
Spring MVC, Sun JSF-RI, AJAX, or MyFaces are supported.
</listitem>
- </itemizedlist>
+ </itemizedlist>
<para>
- <emphasis role="bold">Web Services for Remote Portlets</emphasis>
- </para>
- <itemizedlist>
- <listitem>
- <emphasis role="bold">WSRP Consumer</emphasis>
- <itemizedlist>
- <listitem>Support for WSRP Base level (support for service description and markup interfaces)</listitem>
- <listitem>Ability to easily consume portlets from remote producers</listitem>
- <listitem>Seamless integration of WSRP portlets in portal</listitem>
- <listitem>Support for simple registration schemes</listitem>
- <listitem>Simple caching of markup and metadata</listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <emphasis role="bold">WSRP Producer</emphasis>
- <itemizedlist>
- <listitem>Support for WSRP Base level (support for service description and markup interfaces)</listitem>
- <listitem>Local portlets can easily be exposed remotely to WSRP consumers</listitem>
- <listitem>Includes a local WSRP producer to easily test WSRP in Portal ('self' portlet provider)</listitem>
- </itemizedlist>
-</listitem>
- </itemizedlist>
- <para>
<emphasis role="bold">Themes and Layouts</emphasis>
</para>
<itemizedlist>
@@ -280,5 +255,9 @@
Content can be attributed to a specific locale and then served
to the user based on his/her browser settings.
</listitem>
+ <listitem>
+ <emphasis role="bold">Workflow Support:</emphasis>
+ Basic submit for review and approval process.
+ </listitem>
</itemizedlist>
</preface>
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/intro.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/intro.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/intro.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -6,6 +6,11 @@
<surname>Russo</surname>
<email>roy(a)jboss.org</email>
</author>
+ <author>
+ <firstname>Chris</firstname>
+ <surname>Laprun</surname>
+ <email>chris.laprun(a)jboss.com</email>
+ </author>
</chapterinfo>
<title>JBoss Portal Basics</title>
<sect1>
@@ -40,7 +45,7 @@
</note>
</sect2>
<sect2 id="intro_portal_pages">
- <title>Portal Pages</title>
+ <title>Pages</title>
<para>A Portal Page is an aggregator of Portlet Windows. It is generated by the portal, during the reponse
phase. During this phase, the portal aggregates all of the HTML markup created the individual portlets,
decorates them with window controls, and presents them to the user as a consolidated page.
@@ -77,28 +82,30 @@
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">Window Title</emphasis>
+ <emphasis role="bold">Window Title:</emphasis>
Defines the content and purpose of the individual portlet window.
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Window Fragment</emphasis>
- The generated HTML markup produced by the portlet on the server-side.
+ <emphasis role="bold">Window Fragment:</emphasis>
+ Generated HTML markup produced by the portlet on the server-side.
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Window Controls</emphasis>
- Window controls are divided in to two categories:
- <emphasis role="bold">Window State</emphasis>
- and
- <emphasis role="bold">Portlet Mode</emphasis>
- .
+ <emphasis role="bold">Window Controls:</emphasis>
+ Window controls are divided into two categories and control different aspects of how the user can
+ impact the generated markup. Each window control can be click to interact with the window in
+ specific way. <emphasis role="bold">Window State</emphasis> icons control how much room the window
+ will take on the page and how much markup will be shown.
+ <emphasis role="bold">Portlet Mode</emphasis> icons, on the other hand, control the mode in which
+ the portlet operate, thus impacting the type of generated markup. Note that not all portlets
+ support all defined window states and/or portlet modes.
<itemizedlist>
<listitem>
<para>
- <emphasis role="bold">Window State:</emphasis>
+ <emphasis role="bold">Window State icons and their meaning:</emphasis>
<itemizedlist>
<listitem>
<para>
@@ -106,8 +113,9 @@
<imagedata fileref="images/intro/ico_16_normal.gif" format="gif"/>
</imageobject>
<emphasis role="bold">(Normal)</emphasis>
- - Normal window state, is what you see in the illustration above. All portlet
- windows take up a similar amount of space on the page.
+ - Normal window state, is the most common state for portlets (portlets in the
+ above image are in the normal window state). All portlet
+ windows occupy a similar amount of space on the page.
</para>
</listitem>
<listitem>
@@ -116,7 +124,7 @@
<imagedata fileref="images/intro/ico_16_minimize.gif" format="gif"/>
</imageobject>
<emphasis role="bold">(Minimized)</emphasis>
- - The portlet window renders, minimal-to-no markup.
+ - The portlet is instructed to render minimal-to-no markup.
</para>
</listitem>
<listitem>
@@ -124,34 +132,39 @@
<imagedata fileref="images/intro/ico_16_maximize.gif" format="gif"/>
</imageobject>
<emphasis role="bold">(Maximized)</emphasis>
- - The portlet window takes up a maximum amount of real estate on the page.
+ - The portlet window can occupy as much space of real estate on the page.
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Portlet Mode:</emphasis>
+ <emphasis role="bold">Portlet Modes and their meaning:</emphasis>
+ Portlet modes are not always available (it depends on the portlet support for a given mode).
+ Moreover, the Edit mode is only available to logged in users, as in this mode, the portlet
+ preferences can be modified to be individually suited to a particular user's needs.
<itemizedlist>
<listitem>
<para>
<imageobject>
- <imagedata fileref="images/intro/ico_cancel.gif" format="gif"/>
+ <imagedata fileref="images/intro/ico_edit.gif" format="gif"/>
</imageobject>
- <emphasis role="bold">(View)</emphasis>
- - In View mode, the portlet renders markup reflecting the current window state of
- the portlet. The button is labeled 'Cancel', so the user understand he is leaving
- "Edit Mode" and reverting back to "View Mode". The diagram above has all portlet
- windows in View mode.
+ <emphasis role="bold">(Edit)</emphasis>
+ - Only visible to logged-in users. Allows a logged-in user to customize the
+ portlet's preferences.
</para>
</listitem>
<listitem>
<para>
<imageobject>
- <imagedata fileref="images/intro/ico_edit.gif" format="gif"/>
+ <imagedata fileref="images/intro/ico_cancel.gif" format="gif"/>
</imageobject>
- <emphasis role="bold">(Edit)</emphasis>
- - Allows a user to customize the portlet's behaviour.
+ <emphasis role="bold">(Return to View mode)</emphasis>
+ - The button labeled 'Cancel' is only visible when a user is logged in and the
+ portlet associated to the current window is in the Edit mode. This replaces the
+ Edit button so the user understands that by clicking it she will leave the
+ "Edit Mode" and reverting back to "View Mode". Portlets are by default in View
+ mode.
</para>
</listitem>
<listitem>
@@ -160,7 +173,8 @@
<imagedata fileref="images/intro/ico_16_help.gif" format="gif"/>
</imageobject>
<emphasis role="bold">(Help)</emphasis>
- - A portlet should provide help information to the user.
+ - Allows a user to access helpful information about the portlet, if it provides
+ it (which is recommended).
</para>
</listitem>
</itemizedlist>
@@ -174,107 +188,89 @@
</sect2>
</sect1>
<sect1 id="contents_pages">
- <title>The Portal Pages</title>
+ <title>Default Portal installation</title>
+ <para>
+ This section will take a quick look at the default Portal installation and the pages and portlets that come
+ with it.
+ </para>
<sect2>
- <title>Navigating the Portal Pages</title>
- <para>Navigating the portal pages is normally performed either by typing in a specific URL (
- <xref linkend="intro_portal_pages"/>
- ), or using the Navigation Tabs at the top of the page.
+ <title>Default Portal Pages</title>
+ <para>Three pages are available in the default Portal: Home, News and Weather. You can access pages either by
+ entering the page URL in your browser location bar, as shown in <xref linkend="intro_portal_pages"/>, or
+ by clicking the tab associated to the page in the Navigation Tabs at the top of the page.
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/tabs.gif" format="gif" align="center" valign="middle"/>
+ <imagedata fileref="images/intro/tabs.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
</para>
- <para>Take note, also, that the navigation tabs support sub-page navigation as well. By hovering over a tab
- with childPages, it will display a flyout menu for those subpages
+ <note>Navigation tabs support sub-page navigation as well. By hovering over a tab
+ with child Pages, it will display a flyout menu for those subpages:
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/nav_sub.gif" format="gif" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- </para>
- <para>Altervatively, once logged in, you are able to navigate to your Dashboard or the Admin Portal by using
- the navigation elements, located in the top-right of the main portal page.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/nav2.gif" format="gif" align="center" valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
+ There are no pages with subpages in the default Portal installation.
+ </note>
<para>
- Each page, in the default installation of JBoss Portal is explained in the following sections, along with
- the portlets found
- within them.
+ While you can use a Portal anonymously, it is much more interesting to do so while logged in, as you get the
+ opportunity to customize the content you want to see or even create your own personal Dashboard, as
+ explained in <xref linkend="dashboard"/>.
</para>
</sect2>
- <sect2 id="logging_ing">
+ <sect2 id="logging_in">
<title>Logging in to the Portal</title>
<para>Logging in to the portal is accomplished by clicking the
- <emphasis>Login</emphasis>
- link at the top-right of the portal page. You can login, using the following credentials:
- <programlisting>
- <![CDATA[
-user/user
-admin/admin
- ]]>
- </programlisting>
+ <emphasis>Login</emphasis> link at the top-right of the portal page. Portal will present you with a logging
+ screen where you can enter your credentials:
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/login_ss.gif" format="gif" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
+
+ The default Portal installation
+ defines two users: a regular user with no special privileges
+ (login: <literal>user</literal>, password: <literal>user</literal>) and an
+ administrator user who can alter Portal's content (login: <literal>admin</literal>, password:
+ <literal>admin</literal>).
+
</para>
<para>
- Once logged in, the top-right menu will change so you can then navigate to your personal dashboard and other
- functionality that is included therein.
+ Once logged in, the top-right menu will change so you can then navigate to your personal dashboard or log
+ out. If you have access to other portal instances, they will be shown here as well.
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/login.gif" format="gif" align="center"
- valign="middle"/>
+ <imagedata fileref="images/intro/logged.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
<note>If you login as an administrator, you will also be presented with a link to the
- <emphasis>Admin</emphasis>
- portal.
+ <emphasis>Admin</emphasis> portal.
</note>
</para>
</sect2>
<sect2>
- <title>Default Page</title>
- <para>The default page contains the following portlets:
- <itemizedlist>
- <listitem>
- <xref linkend="intro_greetings_portlet"/>
- </listitem>
- <listitem>
- <xref linkend="intro_user_portlet"/>
- </listitem>
- <listitem>
- <xref linkend="intro_cms_portlet"/>
- </listitem>
- </itemizedlist>
- </para>
+ <title>Home Page</title>
<sect3 id="intro_greetings_portlet">
<title>Greetings Portlet</title>
<para>
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/greetings_portlet.gif" format="gif" align="center"
- valign="middle"/>
+ <imagedata fileref="images/intro/greetings.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
Displays hard-coded links to downloading JBoss Portal, downloading
- portlets from PortletSwap.com, and the live online JBoss Portal demo. It also contains default
- authentication information on loging in.
+ portlets from <ulink url="http://www.portletswap.com">PortletSwap</ulink>, and the live online JBoss
+ Portal demo. It also contains default authentication information on loging in, as well as a link to the
+ official Portal documentation.
</para>
</sect3>
<sect3 id="intro_user_portlet">
<title>User Portlet</title>
- <note>Administrators should view,
- <xref linkend="useradmin"/>
- , for managing the portal Userbase. Only user operations are covered in this section...
+ <note>Administrators should view <xref linkend="useradmin"/> for managing the portal user base. Only user
+ operations are covered in this section...
</note>
<para>
<mediaobject>
@@ -289,7 +285,7 @@
is covered in the following sections.
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/user_portlet_loggedin.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/user_portlet_loggedin.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
@@ -300,31 +296,23 @@
<emphasis role="bold">Create a new account</emphasis>
</para>
<para>
+ Create a new account by clicking on the <emphasis>"You can create an account"</emphasis>
+ link at the bottom of the portlet, when not logged. A User can then fill in the necessary
+ information to create an account on the system:
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/user_portlet_create.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/user_portlet_create.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
- Create a new account by clicking on the
- <emphasis>Create</emphasis>
- link in the portlet. A User can then fill in the necessary information to create an account on
- the system:
</para>
</listitem>
<listitem>
<para>
- <emphasis role="bold">Edit personal information.</emphasis>
+ <emphasis role="bold">Edit personal information</emphasis>
</para>
<para>A user has the ability to edit his personal information at any time by clicking on the
- <emphasis>Edit Info</emphasis>
- link.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/user_portlet_editinfo.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
+ <emphasis>"Edit your profile"</emphasis> link, when logged in.
</para>
</listitem>
</itemizedlist>
@@ -335,23 +323,17 @@
<para>
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/cms_portlet.gif" format="gif" align="center"
- valign="middle"/>
+ <imagedata fileref="images/intro/cms_portlet.gif" format="gif" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- Renders data from the Content Management System embedded with the Portal. Users are able to
- navigate the content, view images, binary files, etc.. via this portlet.
+ Portal includes a basic Content Management System (CMS). Portal provides a CMS portlet which allows users
+ to navigate the CMS content (static html, images, binary files, etc.).
</para>
<para>
Displaying content is done by the portal using a path mapper. For example, if we wanted to display a zip
- file, located in
- <emphasis>/default/foo/bar.zip</emphasis>
- , we would type in the URL
- <emphasis>http://localhost:8080/content/default/foo/bar.zip</emphasis>
- .
- <emphasis role="bold">Notice how the path to the content, is prefixed with the '/content'
- term.
- </emphasis>
+ file, located in <emphasis>/default/foo/bar.zip</emphasis>, we would type in the URL
+ <emphasis>http://localhost:8080/content/default/foo/bar.zip</emphasis>.
+ <emphasis role="bold">Notice how the path to the content, is prefixed with the '/content' term.</emphasis>
Although in this example we are describing binary content retrieval, the same is to be said for text/html
files. Keep in mind, however, that binary files are displayed outside of the portal pages, but text/html
are displayed inside the CMSPortlet Window.
@@ -363,10 +345,7 @@
and retrieve the Spanish version of that file. If a Spanish version is not found, it will then try and
retrieve the default language version set for the CMSPortlet (set to English, by default).
</para>
- <note>Administrators should view,
- <xref linkend="admincmsPortlet"/>
- , for managing the data in the CMS.
- </note>
+ <note>Administrators should read <xref linkend="admincmsPortlet"/> for managing the data in the CMS.</note>
</sect3>
</sect2>
<sect2>
@@ -374,22 +353,43 @@
<para>
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/newspage.gif" format="gif" align="center" valign="middle"/>
+ <imagedata fileref="images/intro/newspage.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- The News Page contains customizable weather and news displays from common internet feeds. An open internet
+ The News Page contains 2 portlets displaying news from common internet feeds. An open internet
connection on the server-side is therefore required for them to operate. ;-)
</para>
+ <sect3 id="newsportlet">
+ <title>News Portlet</title>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/intro/newsportlet.png" format="png" align="center" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ The News Portlet retrieves an RSS news feed from a URL and displays it as HTML to the user.
+ </para>
+ <para>Additionally, a logged-in user is able to modify her preference in RSS feed source by using the
+ Portlet's Edit Mode (click
+ <imageobject>
+ <imagedata fileref="images/intro/ico_edit.gif" format="gif"/>
+ </imageobject>
+ ). Once the form is submitted, this property will be saved
+ in the user's preference, so she will always see the same news source, when logged in.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/intro/newsportlet_edit.png" format="png" align="center"
+ valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <note>This portlet is capable of handling most RSS 1.0 and RSS 2.0 feeds.</note>
+ </sect3>
+ </sect2>
+ <sect2>
+ <title>Weather Page</title>
<para>
- This page contains the following portlets:
- <itemizedlist>
- <listitem>
- <xref linkend="weatherportlet"/>
- </listitem>
- <listitem>
- <xref linkend="newsportlet"/>
- </listitem>
- </itemizedlist>
+ This page contains a portlet displaying the weather forecast for a specific location.
</para>
<sect3 id="weatherportlet">
<title>Weather Portlet</title>
@@ -400,16 +400,15 @@
</imageobject>
</mediaobject>
The Weather Portlet retrieves an RSS weather feed, based on a key (commonly a US Postal Code), and
- displays
- it as HTML to the user.
+ displays it as HTML to the user.
</para>
- <para>Additionally, a user is able to modify his preference in location by going in to the Portlet's Edit
- Mode (click
+ <para>Additionally, a logged-in user is able to modify her preference in location by using the
+ Portlet's Edit Mode (click
<imageobject>
<imagedata fileref="images/intro/ico_edit.gif" format="gif"/>
</imageobject>
- ). Any valid US Postal Code can be inputted here. Once the form is submitted, this property will be saved
- in the user's preference, so he will always see the same weather data for his location, when logged in.
+ ). Any valid US Postal Code can be input here. Once the form is submitted, this property will be saved
+ in the user's preference, so she will always see the same weather data for her location, when logged in.
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/weatherportlet_edit.gif" format="gif" align="center"
@@ -430,16 +429,15 @@
<para>Enter your city name in the location field, found on the page:
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/weather_config1.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/weather_config1.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
</para>
</listitem>
<listitem>
- <para>Find your location on the list under the form and click on it (In this case, its
- <emphasis>Marseille, France</emphasis>
- ):
+ <para>Find your location on the list under the form and click on it
+ (<emphasis>Marseille, France</emphasis>, in this case):
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/weather_config2.gif" format="gif" align="center"
@@ -449,9 +447,8 @@
</para>
</listitem>
<listitem>
- <para>Copy the location digits from the address bar in your browser (In this case, its
- <emphasis>FRXX0059</emphasis>
- ):
+ <para>Copy the location digits from the address bar in your browser (<emphasis>FRXX0059</emphasis>
+ in this case):
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/weather_config3.gif" format="gif" align="center"
@@ -461,21 +458,18 @@
</para>
</listitem>
<listitem>
- <para>Paste these numbers in to the weather portlet edit form (In this case, its
- <emphasis>FRXX0059</emphasis>
- ):
+ <para>Paste these numbers in to the weather portlet edit form (<emphasis>FRXX0059</emphasis> in
+ this case):
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/weather_config4.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/weather_config4.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
- Hit
- <emphasis>submit</emphasis>
- ...
+ Hit <emphasis>submit</emphasis>...
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/weather_config5.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/weather_config5.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
@@ -484,258 +478,114 @@
</orderedlist>
</para>
</sect3>
- <sect3 id="newsportlet">
- <title>News Portlet</title>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/newsportlet.gif" format="gif" align="center" valign="middle"/>
- </imageobject>
- </mediaobject>
- The News Portlet retrieves an RSS news feed, based on a url, and displays it as HTML to the user.
- </para>
- <para>Additionally, a user is able to modify his preference in RSS feed source by going in to the Portlet's
- Edit
- Mode (click
- <imageobject>
- <imagedata fileref="images/intro/ico_edit.gif" format="gif"/>
- </imageobject>
- ). Once the form is submitted, this property will be saved
- in the user's preference, so he will always see the same news source, when logged in.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/newsportlet_edit.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <note>This portlet is capable of handling most RSS 1.0 and RSS 2.0 feeds.</note>
- </sect3>
</sect2>
- <sect2>
- <title>Test Page</title>
- <para>
- Items in this test page change frequently. They are used mainly by the JBoss Portal Development team to
- debug and test new functionality. For that reason, these items are not covered in this document. It is
- recommended that Portal Administrators remove this page for that reason.
- </para>
- </sect2>
</sect1>
<sect1 id="dashboard">
<title>Personal Dashboard</title>
- <para>Once logged in, all users/administrations of the portal will have a personal dashboard they can navigate to,
- by clicking the
- <emphasis>My Dashboard</emphasis>
- link at the top-right of the portal page.
+ <para>Once logged in, all users/administrations of the portal can access a personal dashboard by clicking the
+ <emphasis>Dashboard</emphasis> link at the top-right of the portal page.
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/dashboard.jpg" format="jpg" align="center"
- valign="middle"/>
+ <imagedata fileref="images/intro/dashboard.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
The personal dashboard allows users to customize their portal pages however they like, and all changes will be
persisted... so the next time the user logs in to his dashboard, he will see the previous changes he made.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/dashboard_dnd.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
While navigating any of the dashboard pages, a user will be able to drag and drop portlet windows to any
- location, if the administrator allows this functionality. Changes made in this fashion will be persisted.
+ location, if the administrator allows this functionality. Changes made in this fashion will also be persisted.
</para>
<para>
+ It is also possible to copy the content of a shared page to your dashboard so you can customize it to your
+ liking. Just click the <emphasis>'Copy to my dashboard'</emphasis> link at the top right of the page.
+ This will clone the page and add it to your personal dashboard as a page with the same name.
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/dashboard_add.gif" format="gif" align="center"
- valign="middle"/>
+ <imagedata fileref="images/intro/dashboard_copy_to.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- You are also able to add(clone) shared pages to your personal dashboard, by selecting the
- <emphasis>Add to Dashboard</emphasis>
- link. This will clone the page and add it to your personal dashboard as a page with the same name.
</para>
<sect2 id="dashboard_configure">
<title>Configuring your personal dashboard</title>
<para>
- A user is able to configure his personal dashboard, by accessing the Configurator, using the top-right menu
- item, labeled
- <emphasis>Edit Content</emphasis>
- . He should then see the main Configurator screen:
+ You can configure your dashboard by using the top-right menu item labeled <emphasis>'Edit Page'</emphasis>:
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/dashboard_configure.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/dashboard_configure.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
- From this screen, a user is able to perform configuration actions on his dashboard, by first selecting the
- page he would like to edit, using the page selector dropdown:
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/dashboard_selectpage.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- The possible actions on a selected page are as follows:
- <itemizedlist>
- <listitem>
- <xref linkend="dashboard_createpages"/>
- </listitem>
- <listitem>
- <xref linkend="dashboard_assignportlets"/>
- </listitem>
- <listitem>
- <xref linkend="dashboard_assignthemes"/>
- </listitem>
- <listitem>
- <xref linkend="dashboard_deletepage"/>
- </listitem>
- </itemizedlist>
</para>
- <sect3 id="dashboard_createpages">
- <title>Creating Pages</title>
+ <sect3>
+ <title>Dashboard-wide operations</title>
<para>
- A user is able to create new pages in his personal dashboard by simply entering a desired Page name in
- the
- <emphasis>Create New Page</emphasis>
- dialogue.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/dashboard_createpage.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
+ You can select a theme and layout for your dashboard by selecting from the available ones and then
+ clicking on select in the <emphasis>Theme and Layout</emphasis> form.
+ </para>
+ <para>
+ You can also create new pages that will be added to your dashboard by simply entering the name of the new
+ page in the <emphasis>Create New Page</emphasis> form at the top left of the screen.
<note>
<itemizedlist>
<listitem>Page names must be unique.</listitem>
<listitem>Page names cannot be blank.</listitem>
</itemizedlist>
</note>
- Upon creating a new page, the Configurator will refresh and allow a user to customize the new page.
+ Upon creating a new page, the screen will refresh and allow a user to customize the new page.
</para>
+ <para>
+ You may delete dashboard pages at any time, by first selecting the page you want to delete using the
+ popup menu at the top of the screen and then clicking the <emphasis>Delete this page</emphasis> button
+ at the bottom of the screen. We will note that users are not able to delete the default dashboard page.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/intro/dashboard_deletepage.png" format="png" align="center" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ <warning>
+ Deleted pages are NOT recoverable. This change is permanent!
+ </warning>
+ </para>
</sect3>
<sect3 id="dashboard_assignportlets">
- <title>Managing Portlets</title>
+ <title>Managing Portlets on a page</title>
<para>
+ You can add, remove and reorder portlets on a dashboard page to adapt your environment to your liking.
+ To do so, just select the page you want to modify using the page popup selector and use the portlet
+ management form. We will not explain how to use it here as it is similar to the page layout functionality
+ of the Admin portal, which we will look at in <xref linkend="page_configuration"/>
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/dashboard_assignportlets.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/dashboard_assignportlets.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
- This section of the Configurator allows users to add, remove, and reorder portlets on a selected
- dashboard
- page.
</para>
- <para>
- <emphasis role="bold">Assigning portlets</emphasis>
- to a page is accomplished by selecting which portlets you would like added to a page
- from the
- <emphasis>Available Content</emphasis>
- list. (You may select multiple portlets by holding CTRL and clicking on the available portlets.) Once you
- have selected which portlet you would like to assign to a specific column, click the
- <imageobject>
- <imagedata fileref="images/intro/portlet_assign.gif" format="gif"/>
- </imageobject>
- button next to the target column.
- </para>
- <para>
- <emphasis role="bold">Removing portlets</emphasis>
- from a page is accomplished by selecting which portlets you would like removed from a
- specific column. (You may select multiple portlets by holding CTRL and clicking on the available
- portlets.)
- Once you
- have selected which portlet you would like removed, click the
- <imageobject>
- <imagedata fileref="images/intro/portlet_remove.gif" format="gif"/>
- </imageobject>
- button next to the source column.
- </para>
- <para>
- <emphasis role="bold">Sorting portlets</emphasis>
- in a column is accomplished by selecting which portlets you would like to sort from a
- specific column. (You may select multiple portlets by holding CTRL and clicking on the available
- portlets.)
- Once you
- have selected which portlet you would like re-ordered, click the
- <imageobject>
- <imagedata fileref="images/intro/portlet_up.gif" format="gif"/>
- </imageobject>
- or
- <imageobject>
- <imagedata fileref="images/intro/portlet_down.gif" format="gif"/>
- </imageobject>
- button next to the source column.
- </para>
</sect3>
- <sect3 id="dashboard_assignthemes">
- <title>Managing Theme and Layouts</title>
- <para>
- Using the Theme and Layout dropdowns, the configurator allows for theme and/or layout assignment to a
- specific dashboard page. The user simply selects the desired theme and/or layout and presses
- <emphasis>Select</emphasis>
- to assign it to the page.
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/dashboard_assignthemes.gif" format="gif" align="center"
- valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- </sect3>
- <sect3 id="dashboard_deletepage">
- <title>Deleting Pages</title>
- <para>
- Users may delete dashboard pages at any time, by scrolling to the bottom of the Configurator screen and
- clicking the
- <emphasis>Delete this page</emphasis>
- button. We will note that users are not able to delete the default dashboard page.
- <warning>
- Deleted pages are NOT recoverable. This change is permanent!
- </warning>
- </para>
- </sect3>
</sect2>
</sect1>
<sect1 id="adminportal">
<title>Admin Portal</title>
<para>
- <note>You
- <emphasis role="bold">must be</emphasis>
- logged in as an administrator, or have proper priviledges to see this page.
+ <note>You <emphasis role="bold">must be</emphasis> logged in as an administrator, or have proper priviledges
+ to see this portal.
</note>
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/adminpage.gif" format="gif" align="center" valign="middle"/>
+ <imagedata fileref="images/intro/adminportal.png" format="png" align="center" valign="middle"/>
</imageobject>
</mediaobject>
- The Admin Page's purpose is to allow an administrator to manage all aspects of the portal (Follow the links
- for in-depth reviews of
- these functions):
+ The Admin Portal's purpose is to allow an administrator to manage all aspects of the portal (Follow the links
+ for in-depth reviews of these functions):
<itemizedlist>
- <listitem>
- <para>Users/Roles (See:
- <xref linkend="useradmin"/>
- ,
- <xref linkend="roleadmin"/>
- )
- </para>
+ <listitem>Users/Roles (See: <xref linkend="useradmin"/>, <xref linkend="roleadmin"/>)</listitem>
+ <listitem>Content Management System (See: <xref linkend="admincmsPortlet"/>)</listitem>
+ <listitem>Portal Objects (themes, layouts, portal instances, pages, windows, security, and deployed
+ portlets) (See: <xref linkend="dynamicity"/>)</listitem>
+ <listitem>WSRP (See the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/wsrp.html">WSRP chapter</ulink>
+ in the Reference Guide for more information)
</listitem>
- <listitem>
- <para>Content Management System (See:
- <xref linkend="admincmsPortlet"/>
- )
- </para>
- </listitem>
- <listitem>
- <para>Portal Objects (themes, layouts, portal instances, pages, windows, security, and deployed
- portlets) (See:
- <xref linkend="dynamicity"/>
- )
- </para>
- </listitem>
</itemizedlist>
-
</para>
</sect1>
</chapter>
\ No newline at end of file
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/overview.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/overview.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/overview.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -2,7 +2,7 @@
<title>JBoss Portal - Overview</title>
<para>
<imageobject>
- <imagedata fileref="images/setup/default_ss.jpg" format="jpg" align="center"
+ <imagedata fileref="images/setup/default_ss.png" format="png" align="center"
valign="middle"/>
</imageobject>
</para>
@@ -10,7 +10,7 @@
improving business productivity and reducing costs. Today's top enterprises are realizing this
goal by deploying enterprise portals within their IT infrastructure. Enterprise portals
simplify access to information by providing a single source of interaction with corporate
- information. Although today?s packaged portal frameworks help enterprises launch portals more
+ information. Although today's packaged portal frameworks help enterprises launch portals more
quickly, only JBoss Portal can deliver the benefits of a zero-cost open source license
combined with a flexible and scalable underlying platform.</para>
<para>JBoss Portal provides an open source and standards-based environment for hosting and
@@ -22,11 +22,12 @@
url="http://www.jboss.com/company/aboutopensource">LGPL</ulink>
open source license and is
supported by
- <ulink url="http://www.jboss.com/services/index">JBoss Inc. Professional Support
- and Consulting</ulink>
+ <ulink url="http://www.jboss.com/services/index">Red Hat Middleware, LLC Professional Support
+ and Consulting
+ </ulink>
. JBoss support services are available to assist you in designing,
developing, deploying, and ultimately managing your portal environment. JBoss Portal is
- currently developed by JBoss, Inc. developers, Novell developers, and community contributors.
+ currently developed by Red Hat Middleware, LLC developers and community contributors.
</para>
<para>The JBoss Portal framework and architecture includes the portal container and supports a
wide range of features including standard portlets, single sign-on, clustering and
@@ -76,4 +77,8 @@
</listitem>
</orderedlist>
</para>
+ <para>The JBoss Portal team encourages you to use this guide to install and configure JBoss
+ Portal. If you encounter any configuration issues or simply want to take part in our
+ community, we would love to hear from you in our forums.
+ </para>
</preface>
Deleted: docs/trunk/userGuide/en/images/intro/weather_config4.gif
===================================================================
(Binary files differ)
Added: docs/trunk/userGuide/en/images/intro/weather_config4.png
===================================================================
(Binary files differ)
Property changes on: docs/trunk/userGuide/en/images/intro/weather_config4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Deleted: docs/trunk/userGuide/en/images/intro/weather_config5.gif
===================================================================
(Binary files differ)
Added: docs/trunk/userGuide/en/images/intro/weather_config5.png
===================================================================
(Binary files differ)
Property changes on: docs/trunk/userGuide/en/images/intro/weather_config5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: docs/trunk/userGuide/en/modules/intro.xml
===================================================================
--- docs/trunk/userGuide/en/modules/intro.xml 2007-06-29 10:29:17 UTC (rev 7641)
+++ docs/trunk/userGuide/en/modules/intro.xml 2007-06-29 11:59:43 UTC (rev 7642)
@@ -462,14 +462,14 @@
this case):
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/weather_config4.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/weather_config4.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
Hit <emphasis>submit</emphasis>...
<mediaobject>
<imageobject>
- <imagedata fileref="images/intro/weather_config5.gif" format="gif" align="center"
+ <imagedata fileref="images/intro/weather_config5.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7641 - in docs: tags/JBoss_Portal_2_6_0/userGuide/en/modules and 2 other directories.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2007-06-29 06:29:17 -0400 (Fri, 29 Jun 2007)
New Revision: 7641
Modified:
docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/acknowledgements.xml
docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml
docs/trunk/referenceGuide/en/modules/acknowledgements.xml
docs/trunk/userGuide/en/modules/acknowledgements.xml
Log:
Fix ack chapter
Modified: docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/acknowledgements.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/acknowledgements.xml 2007-06-29 10:13:48 UTC (rev 7640)
+++ docs/tags/JBoss_Portal_2_6_0/referenceGuide/en/modules/acknowledgements.xml 2007-06-29 10:29:17 UTC (rev 7641)
@@ -25,7 +25,7 @@
<listitem>
A few Red Hat employees, Remy Maucherat for Tomcat configuration, Magesh Kumar Bojan and Martin Putz always there to help our customers,
Prabhat Jha for making sure that JBoss Portal runs great everywhere. Noel Rocher for his early feedback on JBoss Portal 2.6
- and contributions. James Cobb for the renaissance theme.
+ and contributions. James Cobb for the Renaissance theme.
</listitem>
<listitem>
The JBoss Labs (http://www.JBoss.org) team for building a great infrastructure on top of JBoss Portal 2.6, providing very useful feedback and
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml 2007-06-29 10:13:48 UTC (rev 7640)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml 2007-06-29 10:29:17 UTC (rev 7641)
@@ -9,9 +9,12 @@
</listitem>
<listitem>
Mark Fernandes and Paul Tamaro from Novell, for their hard work in supplying the
- portal project with usable and attractive themes and layouts in the 2.4 version of JBoss Portal
+ portal project with usable and attractive themes and layouts in the 2.4 version of JBoss Portal.
</listitem>
<listitem>
+ Martin Holzner from Novell, for his work on themes in the 2.4 version of JBoss Portal.
+ </listitem>
+ <listitem>
Kev "kevs3d" Roast for supplying us with two working portlets that integrate existing
frameworks in to the portal: Sun JSF-RI and Spring MVC Portlet.
</listitem>
@@ -22,7 +25,7 @@
<listitem>
A few Red Hat employees, Remy Maucherat for Tomcat configuration, Magesh Kumar Bojan and Martin Putz always there to help our customers,
Prabhat Jha for making sure that JBoss Portal runs great everywhere. Noel Rocher for his early feedback on JBoss Portal 2.6
- and contributions. James Cobb for the renaissance theme.
+ and contributions. James Cobb for the Renaissance theme.
</listitem>
<listitem>
The JBoss Labs (http://www.JBoss.org) team for building a great infrastructure on top of JBoss Portal 2.6, providing very useful feedback and
Modified: docs/trunk/referenceGuide/en/modules/acknowledgements.xml
===================================================================
--- docs/trunk/referenceGuide/en/modules/acknowledgements.xml 2007-06-29 10:13:48 UTC (rev 7640)
+++ docs/trunk/referenceGuide/en/modules/acknowledgements.xml 2007-06-29 10:29:17 UTC (rev 7641)
@@ -19,16 +19,13 @@
frameworks in to the portal: Sun JSF-RI and Spring MVC Portlet.
</listitem>
<listitem>
- Martin Holzner from Novell, for his work on themes in the 2.4 version of JBoss Portal.
- </listitem>
- <listitem>
Swarn "sdhaliwal" Dhaliwal for supplying us with the Struts-Bridge, that will allow
for existing struts applications to work with the Portal.
</listitem>
<listitem>
A few Red Hat employees, Remy Maucherat for Tomcat configuration, Magesh Kumar Bojan and Martin Putz always there to help our customers,
Prabhat Jha for making sure that JBoss Portal runs great everywhere. Noel Rocher for his early feedback on JBoss Portal 2.6
- and contributions. James Cobb for the renaissance theme.
+ and contributions. James Cobb for the Renaissance theme.
</listitem>
<listitem>
The JBoss Labs (http://www.JBoss.org) team for building a great infrastructure on top of JBoss Portal 2.6, providing very useful feedback and
Modified: docs/trunk/userGuide/en/modules/acknowledgements.xml
===================================================================
--- docs/trunk/userGuide/en/modules/acknowledgements.xml 2007-06-29 10:13:48 UTC (rev 7640)
+++ docs/trunk/userGuide/en/modules/acknowledgements.xml 2007-06-29 10:29:17 UTC (rev 7641)
@@ -25,7 +25,7 @@
<listitem>
A few Red Hat employees, Remy Maucherat for Tomcat configuration, Magesh Kumar Bojan and Martin Putz always there to help our customers,
Prabhat Jha for making sure that JBoss Portal runs great everywhere. Noel Rocher for his early feedback on JBoss Portal 2.6
- and contributions. James Cobb for the renaissance theme.
+ and contributions. James Cobb for the Renaissance theme.
</listitem>
<listitem>
The JBoss Labs (http://www.JBoss.org) team for building a great infrastructure on top of JBoss Portal 2.6, providing very useful feedback and
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7640 - docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2007-06-29 06:13:48 -0400 (Fri, 29 Jun 2007)
New Revision: 7640
Modified:
docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml
Log:
James we love you
Modified: docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml
===================================================================
--- docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml 2007-06-29 08:19:17 UTC (rev 7639)
+++ docs/tags/JBoss_Portal_2_6_0/userGuide/en/modules/acknowledgements.xml 2007-06-29 10:13:48 UTC (rev 7640)
@@ -22,7 +22,7 @@
<listitem>
A few Red Hat employees, Remy Maucherat for Tomcat configuration, Magesh Kumar Bojan and Martin Putz always there to help our customers,
Prabhat Jha for making sure that JBoss Portal runs great everywhere. Noel Rocher for his early feedback on JBoss Portal 2.6
- and contributions.
+ and contributions. James Cobb for the renaissance theme.
</listitem>
<listitem>
The JBoss Labs (http://www.JBoss.org) team for building a great infrastructure on top of JBoss Portal 2.6, providing very useful feedback and
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7639 - tags/JBoss_Portal_2_6_0_CR3/faces/src/main/org/jboss/portal/faces/portlet.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2007-06-29 04:19:17 -0400 (Fri, 29 Jun 2007)
New Revision: 7639
Modified:
tags/JBoss_Portal_2_6_0_CR3/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java
Log:
facelet config fix rollback on CR3, my bad
Modified: tags/JBoss_Portal_2_6_0_CR3/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java
===================================================================
--- tags/JBoss_Portal_2_6_0_CR3/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java 2007-06-29 08:13:17 UTC (rev 7638)
+++ tags/JBoss_Portal_2_6_0_CR3/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java 2007-06-29 08:19:17 UTC (rev 7639)
@@ -32,12 +32,7 @@
import javax.portlet.PortletSecurityException;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
-import javax.portlet.PortletContext;
-import javax.faces.context.FacesContext;
-import javax.faces.application.ViewHandler;
import java.io.IOException;
-import java.lang.reflect.Field;
-import java.util.Map;
/**
* JSF portlet which works with every JSF implementation existing on my radar.
@@ -87,32 +82,6 @@
// Proceed to life cycle
PortletConfig bridgeConfig = new JSFMetaBridgePortletConfig(config, metaBridge);
bridgePortlet.init(bridgeConfig);
-
-
- // If we do that it means we are desesperate to make the same JSF app work in a
- // a portlet environment with different JSF impl and different bridges
- // it's 5:00 AM in the morning and that kind of stuff deserves a good rant
- if (metaBridge instanceof SunRIJSFBridge)
- {
- try
- {
- PortletContext portletContext = config.getPortletContext();
- Field servletContextField = portletContext.getClass().getDeclaredField("servletContext");
- servletContextField.setAccessible(true);
- Object servletContext = servletContextField.get(portletContext);
- Field contextField = servletContext.getClass().getDeclaredField("context");
- contextField.setAccessible(true);
- Object context = contextField.get(servletContext);
- Field parametersField = context.getClass().getDeclaredField("parameters");
- parametersField.setAccessible(true);
- Map parameters = (Map)parametersField.get(context);
- parameters.put("facelets.BUILD_BEFORE_RESTORE", "true");
- }
- catch (Exception e)
- {
- e.printStackTrace();
- }
- }
}
public void processAction(ActionRequest request, ActionResponse response) throws PortletException, PortletSecurityException, IOException
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7638 - tags/JBoss_Portal_2_6_0/faces/src/main/org/jboss/portal/faces/portlet.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2007-06-29 04:13:17 -0400 (Fri, 29 Jun 2007)
New Revision: 7638
Modified:
tags/JBoss_Portal_2_6_0/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java
Log:
facelet config fix
Modified: tags/JBoss_Portal_2_6_0/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java
===================================================================
--- tags/JBoss_Portal_2_6_0/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java 2007-06-29 06:22:42 UTC (rev 7637)
+++ tags/JBoss_Portal_2_6_0/faces/src/main/org/jboss/portal/faces/portlet/JSFMetaBridgePortlet.java 2007-06-29 08:13:17 UTC (rev 7638)
@@ -32,7 +32,12 @@
import javax.portlet.PortletSecurityException;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
+import javax.portlet.PortletContext;
+import javax.faces.context.FacesContext;
+import javax.faces.application.ViewHandler;
import java.io.IOException;
+import java.lang.reflect.Field;
+import java.util.Map;
/**
* JSF portlet which works with every JSF implementation existing on my radar.
@@ -82,6 +87,32 @@
// Proceed to life cycle
PortletConfig bridgeConfig = new JSFMetaBridgePortletConfig(config, metaBridge);
bridgePortlet.init(bridgeConfig);
+
+
+ // If we do that it means we are desesperate to make the same JSF app work in a
+ // a portlet environment with different JSF impl and different bridges
+ // it's 5:00 AM in the morning and that kind of stuff deserves a good rant
+ if (metaBridge instanceof SunRIJSFBridge)
+ {
+ try
+ {
+ PortletContext portletContext = config.getPortletContext();
+ Field servletContextField = portletContext.getClass().getDeclaredField("servletContext");
+ servletContextField.setAccessible(true);
+ Object servletContext = servletContextField.get(portletContext);
+ Field contextField = servletContext.getClass().getDeclaredField("context");
+ contextField.setAccessible(true);
+ Object context = contextField.get(servletContext);
+ Field parametersField = context.getClass().getDeclaredField("parameters");
+ parametersField.setAccessible(true);
+ Map parameters = (Map)parametersField.get(context);
+ parameters.put("facelets.BUILD_BEFORE_RESTORE", "true");
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace();
+ }
+ }
}
public void processAction(ActionRequest request, ActionResponse response) throws PortletException, PortletSecurityException, IOException
16 years, 10 months
- 1
- 0
JBoss Portal SVN: r7637 - docs/trunk/userGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: chris.laprun(a)jboss.com
Date: 2007-06-29 02:22:42 -0400 (Fri, 29 Jun 2007)
New Revision: 7637
Modified:
docs/trunk/userGuide/en/modules/dynamicity.xml
Log:
- Added some missing content.
- Improved existing content.
- Added id to section for cross-referencing.
- Fixed typos.
Modified: docs/trunk/userGuide/en/modules/dynamicity.xml
===================================================================
--- docs/trunk/userGuide/en/modules/dynamicity.xml 2007-06-29 05:50:39 UTC (rev 7636)
+++ docs/trunk/userGuide/en/modules/dynamicity.xml 2007-06-29 06:22:42 UTC (rev 7637)
@@ -36,14 +36,14 @@
user session. In order to see the changes on the affected pages, please log out and log back in.
</note>
</sect1>
- <sect1>
+ <sect1 id="management_portlet">
<title>Management Portlet</title>
<note>For the remainder of this chapter, the term <emphasis role="bold">object</emphasis> will be used to mean
Portal, Page, Portlet, or Window indifferently.
</note>
<para>
- The management portlet provides a two-part interface: tabs, corresponding to the different sections that
- can be managed, at the top and the main area under it, displaying the current information for the selected
+ The management portlet provides a two-part interface: tabs, at the top, corresponding to the different sections
+ that can be managed; and the main area under it, displaying the current information for the selected
tab.
<mediaobject>
<imageobject>
@@ -54,20 +54,21 @@
<para>
The tabs are:
<itemizedlist>
- <listitem><emphasis>Portal Objects</emphasis> gathering operations pertaining to managing Portals and their
- pages. This is the most complex part of the interface.</listitem>
+ <listitem><emphasis>Portal Objects</emphasis> gathering operations pertaining to managing portal objects
+ (portal instances, pages, windows and their respective configuration information). This is the most
+ complex part of the interface.</listitem>
<listitem><emphasis>Portlet Instances</emphasis> giving access to all the Portlet instances that have been
configured.</listitem>
<listitem><emphasis>Portlet Definitions</emphasis> giving access to the currently available portlet
providers as well as the Portlets that each provider publishes.</listitem>
- <listitem><emphasis>Dashboards</emphasis> allowing administrators to configure how Dashboards should berrorhandlingaehave.
+ <listitem><emphasis>Dashboards</emphasis> allowing administrators to configure how Dashboards should behave.
</listitem>
</itemizedlist>
We will look at each of these tabs and their functionality in the following sections.
</para>
- <sect2>
+ <sect2 id="admin_portal_objects">
<title>Managing Portal Objects</title>
- <sect3>
+ <sect3 id="portals_operations">
<title>Portals operations</title>
<mediaobject>
@@ -88,36 +89,42 @@
<para>
A link to access server-wide portal properties is located right beneath the breadcrumbs. This allows
- the administrator to set server-wide property and configure how errors should be handled. Please refer
- to the <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/errorhandling...">Error
- handling chapter</ulink> of the Reference Guide for more information on this point.
+ the administrator to set server-wide property and configure how errors should be handled:
<mediaobject>
<imageobject>
<imagedata fileref="images/management/portals_properties.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
+ Please refer to the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/errorhandling...">Error
+ handling chapter</ulink> of the Reference Guide for more information on this point.
</para>
<para>
A form allowing administrator to create new portal instances is located beneath the
<literal>Properties</literal> link. Enter the name of the new portal (which, of course, should be
- different from any of the already existing one) and click on <literal>Add portal</literal> and you'll
- see a new line appear in the portal list located under the form.
+ different from any of the already existing one) and click on <literal>Add portal</literal> and the
+ portal instances list will be refreshed to display the newly created portal instance.
</para>
- <para>The last element of the top level of the <literal>Portal Objects</literal> tab is a table listing
- all the available portal instances along with possible actions on them. Clicking on the portal name
- will display a screen showing the information for this given portal instance, thus drilling down the
- hierarchy of available portal objects.</para>
+ <para>
+ The last element of the top level of the <literal>Portal Objects</literal> tab is a table listing
+ all the available portal instances along with possible actions on them. Clicking on the portal name
+ will display a screen showing the information for this given portal instance, thus drilling down the
+ hierarchy of available portal objects.
+ </para>
- <para>In the next sections we will drill down this hiearchy to look at the default portal and
- one of its pages.</para>
+ <para>
+ In the next sections we will demonstrate the functionality of the management portlet by drilling
+ progressively further down this hiearchy to look at the default portal, one of its pages, show
+ how to configure content on a page and finally, look at a specific window information.
+ </para>
</sect3>
- <sect3>
- <title>Looking at the default Portal</title>
+ <sect3 id="portal_instance_configuration">
+ <title>Looking at a portal instance information</title>
<para>
If you click on the <literal>default</literal> portal in the list of available portal instances on the
@@ -136,7 +143,7 @@
<para>
Links to more information and operations that
affect this portal instance are located beneath the breadcrumbs. We will look at them in turn later.
- We won't look at the <literal>Destroy</literal> operation, which has its name implies, allows an
+ We won't look at the <literal>Destroy</literal> operation, which as its name implies, allows an
administrator to destroy the current portal instance (after a confirmation screen, as the operation is
<emphasis role="bold">NOT</emphasis> undoable). Note that these links mirror the links that were
available in the portal instances list on the top level page.
@@ -150,15 +157,15 @@
<para>
It is also possible to designate one of the portal page as the default page that users are directed
- to when the first access the portal instance. This is done by selecting the page via the page selection
- drop-down menu and then click on <literal>Update</literal>.
+ to when they first access the portal instance. This is done by selecting the page via the page
+ selection drop-down menu and then click on <literal>Update</literal>.
</para>
<para>
Finally, a table displaying the list of available pages for this portal instance is located at the
bottom of this screen. The first column shows the page name, which you can click to drill down the
hierachy and display the information specific to that particular page. The second column, on the other
- hand, provides a list of links to more information on the associated page or actions on it. These links
+ hand, provides a list of action links on the associated page. These links
will be also appearing on individual page screens, as we shall see, just like portal action links
appearing in the portal instances list also appeared on individual portal pages.
</para>
@@ -166,8 +173,7 @@
<para>
Let's now look at the default portal's <literal>Security</literal> information screen. This can be
accessed by clicking the <literal>Security</literal> action link on the portal page. Here, an
- administrator can configure the default policy for security on objects for this portal instance. Note
- the breadcrumbs...
+ administrator can configure the default policy for security on objects for this portal instance:
<mediaobject>
<imageobject>
<imagedata fileref="images/management/default_portal_security.png" format="png" align="center"
@@ -175,14 +181,13 @@
</imageobject>
</mediaobject>
Please refer to the
- <ulink
- url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/security.html">Security</ulink>
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/security.html">Security</ulink>
chapter of the Reference Guide for more information about how to secure portal objects.
</para>
<para>
The <literal>Properties</literal> action link displays the currently configured properties for this
- portal instance and allows you to modify them, as well as configure the error handling strategy.
+ portal instance and allows you to modify them, as well as configure the error handling strategy:
<mediaobject>
<imageobject>
<imagedata fileref="images/management/default_portal_properties.png" format="png" align="center"
@@ -193,7 +198,7 @@
<para>
The <literal>Theme</literal> action link displays a screen where the administrator can configure theme,
- layout and render set for this portal instance.
+ layout and render set for this portal instance:
<mediaobject>
<imageobject>
<imagedata fileref="images/management/default_portal_theme.png" format="png" align="center"
@@ -206,13 +211,13 @@
</para>
<para>
- Now that we have look at portal level information, let's drill down the hierachy again and look at
+ Now that we have looked at portal level information, let's drill down the hierachy again and look at
a page, more precisely the <literal>default</literal> page, by clicking its name in the pages list.
</para>
</sect3>
- <sect3>
- <title>Looking at the default Page of the default Portal</title>
+ <sect3 id="page_configuration">
+ <title>Looking at a page configuration</title>
<para>
<mediaobject>
@@ -221,7 +226,7 @@
valign="middle"/>
</imageobject>
</mediaobject>
- The layout of this screen should start to be familiar. The information for a page looks a lot like the
+ The layout of this screen should start feeling familiar. The information for a page looks a lot like the
information for a portal instance. Note the breadcrumbs indicating that you are indeed looking at a
page. Again, we find the action links at the top of the page, mirroring the ones that were available
for each page in the pages list of the portal instance screen. Once again, you can configure the page's
@@ -229,6 +234,19 @@
</para>
<para>
+ Similarly to other screens in the portal objects hierarchy, a page configuration screen also provides
+ a list of all windows for that page. This list contains two columns: the first one contains the
+ name of the window, while the second one provides a list of action links for that specific window.
+ As usual, clicking on a window name will display information about that window.
+ </para>
+
+ <para>
+ Just like a portal instance can contain several pages, a page can contain several subpages. As such
+ a page defines means to create subpages and set which subpage to display when a user is first directed
+ to the page. These operations work similarly to the same operations at the portal instance level.
+ </para>
+
+ <para>
You can also rename the page if desired:
<mediaobject>
<imageobject>
@@ -239,9 +257,9 @@
</para>
<para>
- Of specific interest, is the <literal>Page Layout</literal> link. This is where you need to go to
- configure which portlet instance will be displayed in which window on which region on the page. Let's
- take a look at this screen and how it works:
+ Of specific interest, though, is the <literal>Page Layout</literal> link. This is where you need to
+ go to configure which portlet instance will be displayed in which window on which region on the page.
+ Let's take a look at this screen and how it works:
<mediaobject>
<imageobject>
<imagedata fileref="images/management/default_page_layout.png" format="png" align="center"
@@ -285,14 +303,13 @@
</imageobject>
</mediaobject>
Note that we could move the window up or down in the region by selecting it in the list and using the
- button to the right of the list, or even destroy the window.
+ button to the right of the list, or even destroy it if desired.
</para>
<para>
We can repeat this process to add content of different types. Let's add a window using a Google widget
- displaying the IP address of the user to the left region of the page. First, enter give a name to your
- window (we'll use "google" here) and select <literal>widget/google</literal> from the content type
- drop-down menu:
+ displaying the IP address of the user. First, give a name to your window (we'll use "google" here)
+ and select <literal>widget/google</literal> from the content type drop-down menu:
<mediaobject>
<imageobject>
<imagedata fileref="images/management/layout_google1.png" format="png" align="center"
@@ -300,14 +317,14 @@
</imageobject>
</mediaobject>
Note how the instances list is replaced by a list of Google widgets. The widget we want to use is
- located in the <literal>Technology</literal> category so select it from the category drop-down menu:
+ located in the <literal>Technology</literal> category, so select it from the category drop-down menu:
<mediaobject>
- <imageobject>
+ <imageobject>
<imagedata fileref="images/management/layout_google2.png" format="png" align="center"
valign="middle"/>
</imageobject>
</mediaobject>
- Press <literal>Search Gadgets</literal> and the widget list will be refreshed, select
+ Press <literal>Search Gadgets</literal> and the widget list will be refreshed. The widget we want is
<literal>MyIP</literal>:
<mediaobject>
<imageobject>
@@ -367,16 +384,9 @@
Integration</ulink> in the Reference Guide. More details on how to setup content roots in CMS are
available in <xref linkend="cmsadmin"/>.
</para>
-
- <para>
- Pages information screens display a list of available windows for that page. Similarly to other
- screens in the portal objects hierarchy, the list contains two columns: the first one contains the
- name of the window, while the second one provides a list of action links for that specific window.
- As usual, clicking on a window name will display information about that window.
- </para>
</sect3>
- <sect3>
+ <sect3 id="window_configuration">
<title>Looking at windows of a given page</title>
<para>
Window operations are similar to the same operations at other level of the hierachy of portal objects.
@@ -394,7 +404,7 @@
</para>
</sect3>
</sect2>
- <sect2>
+ <sect2 id="admin_portlet_instances">
<title>Managing Portlet Instances</title>
<para>
The <literal>Portlet Instances</literal> tab brings the administrator to the list of instances created
@@ -408,7 +418,7 @@
</mediaobject>
</para>
</sect2>
- <sect2>
+ <sect2 id="admin_portlet_definitions">
<title>Managing Portlet Definitions</title>
<para>
The <literal>Portlet Definitions</literal> tab brings the administrator to the list of portlet
@@ -427,15 +437,36 @@
</imageobject>
</mediaobject>
</para>
+ <para>
+ Portlet definitions can be made available by different providers. You can select the provider you want to
+ browse by selecting it in the drop-down menu and clicking <literal>Change</literal>.
+ By default, two providers are available:
+ <itemizedlist>
+ <listitem>
+ <emphasis>local</emphasis>: this is Portal's portlet container. Any successfully deployed portlet will
+ appear in the list of available portlet definitions for this provider.
+ </listitem>
+ <listitem>
+ <emphasis>self</emphasis>: this is Portal's default WSRP consumer configured to consume portlets
+ published by Portal's own WSRP producer. This doesn't have much practical interest apart from allowing
+ a quick test of the WSRP functionality of Portal.
+ </listitem>
+ </itemizedlist>
+ More providers can be added to this list. In particular, any active, properly configured WSRP consumer will
+ also appear in the drop-down menu. Please refer to the
+ <ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/wsrp.html#con...">Consuming
+ remote WSRP portlets in JBoss Portal</ulink> chapter of the Reference Guide for more information on this
+ topic.
+ </para>
</sect2>
- <sect2>
+ <sect2 id="admin_dashboards">
<title>Managing Dashboards</title>
<para>
The <literal>Dashboards</literal> tab allows the administrator to configure parameters for all the user dashboards.
It also allows her to configure the error pages and theme properties as for the other portal objects.
</para>
</sect2>
- <sect2>
+ <sect2 id="admin_wizard">
<title>Wizard mode</title>
<para>
The wizard mode is a fast and easy way to create a new window on a page backed by a portlet instance.
16 years, 10 months
- 1
- 0