Author: julien(a)jboss.com
Date: 2007-06-15 08:03:38 -0400 (Fri, 15 Jun 2007)
New Revision: 7437
Modified:
docs/trunk/referenceGuide/en/modules/contentintegration.xml
docs/trunk/referenceGuide/en/modules/migration.xml
Log:
renaming contentIntegration to contentintegration
Modified: docs/trunk/referenceGuide/en/modules/contentintegration.xml
===================================================================
--- docs/trunk/referenceGuide/en/modules/contentintegration.xml 2007-06-15 12:02:23 UTC
(rev 7436)
+++ docs/trunk/referenceGuide/en/modules/contentintegration.xml 2007-06-15 12:03:38 UTC
(rev 7437)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="contentIntegration">
+<chapter id="contentintegration">
<chapterinfo>
<author>
<firstname>Julien</firstname>
Modified: docs/trunk/referenceGuide/en/modules/migration.xml
===================================================================
--- docs/trunk/referenceGuide/en/modules/migration.xml 2007-06-15 12:02:23 UTC (rev 7436)
+++ docs/trunk/referenceGuide/en/modules/migration.xml 2007-06-15 12:03:38 UTC (rev 7437)
@@ -122,7 +122,7 @@
<para>
This is probably the less trival part to do directly in database. In JBP
2.6 version the way that CMS
content is being displayed changed significantly. Please refer to
- <link linkend="contentIntegration">Content
Integration</link> and <link linkend="cmsPortlet">CMS
Portlet</link>
+ <link linkend="contentintegration">Content
Integration</link> and <link linkend="cmsPortlet">CMS
Portlet</link>
chapters for more information. Basically currently there is no need to
have more than one instance of
<emphasis>CMSPortlet</emphasis> and the portlet window
displays CMS content not by referring to that portlet instance
but by having proper <emphasis>content-type</emphasis>
defined. In "<emphasis>default-object.xml</emphasis>