Author: mmcallis
Date: 2008-02-07 02:15:10 -0500 (Thu, 07 Feb 2008)
New Revision: 9827
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
revising 5.1. JSR-168 Overview, moving 2.3.4.1. Database Setup
2.3.4.2. DataSource Configuration into section 2, instead
of separate sections.
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07
05:31:34 UTC (rev 9826)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/migration.xml 2008-02-07
07:15:10 UTC (rev 9827)
@@ -84,7 +84,8 @@
</imageobject>
</mediaobject>
</para>
- <sect3>
+</sect2>
+ <sect2>
<title>Portlet Names</title>
<para>
Names of certain core bundled portlets have changed. Destroy the following
instances and use the AdminPortlet to recreate them, or, edit the <emphasis
role="bold">JBP_INSTANCES</emphasis> table as follows:
@@ -130,8 +131,8 @@
</listitem>
</orderedlist>
</para>
- </sect3>
- <sect3>
+ </sect2>
+ <sect2>
<title>CMS</title>
<para>
In JBoss Portal 2.6 versions, the way the CMS content is displayed changed
significantly. For further information, please refer to <xref
linkend="contentintegration"/> and <xref
linkend="cmsPortlet"/>. Currently there is no need to have more than one
instance of the <emphasis>CMSPortlet</emphasis>. The portlet window displays
CMS content, not by referring to that portlet instance, but by having the proper
<emphasis>content-type</emphasis> defined. The following configuration is in
the <filename>jboss-portal.sar/conf/data/default-object.xml</filename> file:
@@ -191,8 +192,7 @@
</para>
</note>
</para>
- </sect3>
- </sect2>
+ </sect2>
</sect1>
<!--
<para>This chapter addresses migration issues from version 2.2 to 2.4 of JBoss
Portal.</para>
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-07
05:31:34 UTC (rev 9826)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-07
07:15:10 UTC (rev 9827)
@@ -19,21 +19,11 @@
<title>Portlet Primer</title>
<sect1 id="portlet_primer">
<title>JSR-168 Overview</title>
- <para>The JSR-168 specification aims at defining porlets that can be used by
any JSR-168 portlet container also
- called portals. There are different portals out there with commercial and
non-commercial licences. In this
- chapter we will briefly describe such portlets but for more details you should
read the specifications
- available on the web.</para>
+ <para>The JSR-168 specification aims at defining portlets that can be used by
any JSR-168 portlet container, also known as portals. There are different portals with
commercial and non-commercial licenses. This chapter gives a brief overview of the
<ulink
url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet
Specification</ulink>. Portlet developers are strongly encouraged to read the
<ulink
url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet
Specification</ulink>.
+ </para>
<para>
- <note>This section is a brief overview of the
- <ulink
url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168
Portlet Specification</ulink>
- , and it does not cover the topics in great detail. We strongly encourage
portlet developers to read the
- Specification that can be found
- <ulink
url="http://www.jcp.org/en/jsr/detail?id=168">here</ulink...
- .
- </note>
+ JBoss portal is fully JSR-168 compliant, which means any JSR-168 portlet will
behave as it should inside the portal.
</para>
- <para>As of today, JBoss portal is fully JSR-168 compliant, that means that
any JSR-168 portlet will behave
- as it should inside the portal.</para>
<sect2>
<title>Portal Pages</title>
<para>A portal can be seen as pages with different areas and inside areas,
different windows and each window