From portal-commits at lists.jboss.org Wed Mar 21 16:07:45 2007 Content-Type: multipart/mixed; boundary="===============5547989624395414084==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r6794 - in docs/trunk/referenceGuide/en: images/content and 1 other directories. Date: Wed, 21 Mar 2007 16:07:45 -0400 Message-ID: --===============5547989624395414084== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: julien(a)jboss.com Date: 2007-03-21 16:07:44 -0400 (Wed, 21 Mar 2007) New Revision: 6794 Added: docs/trunk/referenceGuide/en/images/content/ docs/trunk/referenceGuide/en/images/content/after.png docs/trunk/referenceGuide/en/images/content/before.png Modified: docs/trunk/referenceGuide/en/modules/cmsPortlet.xml docs/trunk/referenceGuide/en/modules/contentIntegration.xml Log: adding images to the content integration chapter Added: docs/trunk/referenceGuide/en/images/content/after.png =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 (Binary files differ) Property changes on: docs/trunk/referenceGuide/en/images/content/after.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: docs/trunk/referenceGuide/en/images/content/before.png =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 (Binary files differ) Property changes on: docs/trunk/referenceGuide/en/images/content/before.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: docs/trunk/referenceGuide/en/modules/cmsPortlet.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 --- docs/trunk/referenceGuide/en/modules/cmsPortlet.xml 2007-03-21 19:10:08= UTC (rev 6793) +++ docs/trunk/referenceGuide/en/modules/cmsPortlet.xml 2007-03-21 20:07:44= UTC (rev 6794) @@ -42,7 +42,7 @@ locale, or display content using the default locale setting. -
+
CMS content Since 2.6 displaying CMS content in the portal is done using t= he new content integration feature. Each window of the portal can be configured to display C= MS content directly instead of Modified: docs/trunk/referenceGuide/en/modules/contentIntegration.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 --- docs/trunk/referenceGuide/en/modules/contentIntegration.xml 2007-03-21 = 19:10:08 UTC (rev 6793) +++ docs/trunk/referenceGuide/en/modules/contentIntegration.xml 2007-03-21 = 20:07:44 UTC (rev 6794) @@ -16,6 +16,22 @@ simplifies the configuration: it helps to make content a first class ci= tizen of the portal instead of having an intermediary portlet that holds the content for the portal. The portlet preferences = can still be used to configure how content is displayed to the user. + + + + + + The portal uses portlets to configure content + + + + + + + + The portal references directly the content and use portlet = to interact with content + + Window content The content of a window is defined by @@ -378,9 +394,28 @@ ]]> The web.xml descriptor - You don't need to add the listener class into your war f= ile. As it is provided by the portal - it will always be available. + You don't need to add the listener class into your wa= r file. As it is provided by the portal + it will always be available. + + Configuring window content in deployment descriptor + How to create a portlet that will enable configuration of cont= ent at runtime has been covered above, however + it is also possible to configure content in deployment descriptors. = With our previous example it would give + the following snippet placed in a *-portal.xml = file: + + +MyWindow + + filesystem + /dir1/foo.txt + +center +1 + +]]> + How to configure CMS file this way is covered in the CMS chapt= er: + --===============5547989624395414084==--