3:07 p.m.
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
===================================================================
(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
===================================================================
(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
===================================================================
--- 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.</listitem>
</orderedlist>
</section>
- <section>
+ <section id="configuration-cms_content">
<title>CMS content</title>
<para>Since 2.6 displaying CMS content in the portal is done using the new
content integration
feature. Each window of the portal can be configured to display CMS content
directly instead of
Modified: docs/trunk/referenceGuide/en/modules/contentIntegration.xml
===================================================================
--- 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 citizen 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.</note>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center"
fileref="images/content/before.png" format="png"/>
+ </imageobject>
+ <caption>
+ <para>The portal uses portlets to configure content</para>
+ </caption>
+ </mediaobject>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center"
fileref="images/content/after.png" format="png"/>
+ </imageobject>
+ <caption>
+ <para>The portal references directly the content and use portlet to
interact with content</para>
+ </caption>
+ </mediaobject>
<sect1>
<title>Window content</title>
<para>The content of a window is defined by
@@ -378,9 +394,28 @@
</web-app>
]]></programlisting>
<para>The web.xml descriptor</para>
- <note>You don't need to add the listener class into your war file.
As it is provided by the portal
- it will always be available.</note>
+ <warning>You don't need to add the listener class into your war
file. As it is provided by the portal
+ it will always be available.</warning>
</sect3>
</sect2>
</sect1>
+ <sect1>
+ <title>Configuring window content in deployment descriptor</title>
+ <para>How to create a portlet that will enable configuration of content 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 <emphasis>*-portal.xml</emphasis>
file:
+ </para>
+ <programlisting><![CDATA[
+<window>
+<window-name>MyWindow</window-name>
+<content>
+ <content-type>filesystem</content-type>
+ <content-uri>/dir1/foo.txt</content-uri>
+</content>
+<region>center</region>
+<height>1</height>
+</window>
+]]></programlisting>
+ <note>How to configure CMS file this way is covered in the CMS chapter:
<xref linkend="configuration-cms_content"/></note>
+ </sect1>
</chapter>