Author: thomas.heute(a)jboss.com
Date: 2009-12-02 04:39:19 -0500 (Wed, 02 Dec 2009)
New Revision: 13848
Modified:
docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml
Log:
JBEPP-123: Documentation on how to add custom CMS Interceptors is incorrect
Modified: docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml
===================================================================
--- docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml 2009-12-02 08:55:41 UTC
(rev 13847)
+++ docs/enterprise/trunk/Reference_Guide/en-US/CMS_Portlet.xml 2009-12-02 09:39:19 UTC
(rev 13848)
@@ -45,7 +45,6 @@
</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
having to configure the CMS portlet as it used to be.
</para>
@@ -437,7 +436,7 @@
If you create your own interceptor
<literal>org.example.myCMSInterceptor</literal>, the service descriptor file
will look like:
<programlisting><![CDATA[<mbean
code="org.example.myCMSInterceptor"
name="portal:service=Interceptor,type=Cms,name=MyName" xmbean-dd=""
- xmbean-code="org.jboss.portal.common.system.JBossServiceModelMBean">
+ xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
<xmbean />
</mbean>
@@ -539,6 +538,7 @@
<depends-list-element>
portal:service=Interceptor,type=Cms,name=ApprovalWorkflow
</depends-list-element>
+ <!-- CUSTOM INTERCEPTOR ADDED HERE -->
<depends-list-element>
portal:service=Interceptor,type=Cms,name=MyName
</depends-list-element>