From do-not-reply at jboss.org Tue Jan  8 23:55:46 2013
Content-Type: multipart/mixed; boundary="===============8926036490923873911=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r9038 -
 epp/docs/branches/6.0/Developer_Guide/en-US.
Date: Tue, 08 Jan 2013 23:55:46 -0500
Message-ID: <201301090455.r094tkvY031550@svn01.web.mwc.hst.phx2.redhat.com>

--===============8926036490923873911==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: rdickens
Date: 2013-01-08 23:55:45 -0500 (Tue, 08 Jan 2013)
New Revision: 9038

Modified:
   epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_Develop=
ment.xml
Log:
Updated chapter to version 23 of matching chapter in Confluence portal

Modified: epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_=
Development.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_Develo=
pment.xml	2013-01-07 12:57:14 UTC (rev 9037)
+++ epp/docs/branches/6.0/Developer_Guide/en-US/chapter-4-GDG_Portal_Develo=
pment.xml	2013-01-09 04:55:45 UTC (rev 9038)
@@ -22,11 +22,16 @@
     <para>
             The biggest granularity is what is called &quot;Portal Contain=
ers&quot;. A Portal Container can host multiple &quot;Sites&quot;. Those tw=
o components have a unique identifier that can be found in the default URL =
mapping according to the following scheme: <code><ulink url=3D"http://local=
host:8080/"/>&lt;portalcontainer&gt;/&lt;site&gt; </code>
          </para>
-    <para>
-            When creating a website, it is possible to create a portal con=
tainer from scratch or extend an existing one. It is then possible to exten=
d the portal container which is accessed at <ulink url=3D"http://localhost:=
8080/portal"/> on the out of the box solution, this is the recommended way.=
 While running multiple portal containers is possible, it&apos;s usually be=
tter to keep those on separate installations. Note that multiple websites c=
an run in a single portal container and share some services.
+         <para>
+            When creating a website, you can either create a portal contai=
ner or extend an existing one. Extending an existing portal container, such=
 as the default one provided with JBoss Portal Platform, is the recommended=
 option because you only need to customize it to suit your requirements. An=
other benefit of the extension method is that upgrades consist of copying t=
he newer distribution archives in place of the originals. This upgrade meth=
od is not possible if the distribution archives have been modified.
          </para>
-    <para>
-            By providing an extension you can benefit from the portal prov=
ided by JBoss Portal Platform and be able to customize the parts you want. =
The benefit over directly modifying the shipped files is that it will make =
the updates much easier (by just replacing the archives provided by JBoss P=
ortal Platform). =

+         <para>
+            While running multiple portal containers is possible, it&apos;=
s recommended to keep those on separate installations. Note that multiple w=
ebsites can run in a single portal container and share some services.
+         </para>
+         <para>
+            The procedure for creating portal containers and extending exi=
sting portal containers is similar: create an enterprise archive (EAR) cont=
aining configuration details, runnable code and static resources.
+         </para>
+
             <figure>
         <title>Example</title>
         <mediaobject>


--===============8926036490923873911==--