Author: mmcallis Date: 2008-02-11 16:01:10 -0500 (Mon, 11 Feb 2008) New Revision: 9935 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml Log: revising last two paragraphs for 5.2.1.4. Application Descriptors Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-11 07:52:14 UTC (rev 9934) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-11 21:01:10 UTC (rev 9935) @@ -476,11 +476,13 @@ </para> <para> - Portal 2.6 introduces the notion of <emphasis>content type</emphasis>, which is a generic mechanism to - specify which content will be displayed by a given portlet window. The <literal>window</literal> section - of the previous example can be re-written to take advantage of the new content framework, resulting in - the following deployment descriptor: - <programlisting><![CDATA[<?xml version="1.0" encoding="UTF-8"?> + JBoss Portal 2.6 introduces the notion of <emphasis>content type</emphasis>, which is a generic mechanism to + specify what content will be displayed by a given portlet window. The <computeroutput>window</computeroutput> section + of the previous example, <filename>HelloWorldPortlet/WEB-INF/helloworld-object.xml</filename>, can be re-written to take advantage of the new content framework. The following is an example deployment descriptor that uses the new content framework: + </para> + <para> +<screen><![CDATA[ +<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE deployments PUBLIC "-//JBoss Portal//DTD Portal Object 2.6//EN" "http://www.jboss.org/portal/dtd/portal-object_2_6.dtd"> @@ -498,17 +500,24 @@ <height>1</height> </window> </deployment> -</deployments>]]></programlisting> -</para> -<para> +</deployments>]]> +</screen> + </para> + <para> - This declaration is equivalent to the previous example. We specify that the content being displayed by - the <literal>HelloWorldPortletWindow</literal> is a <literal>portlet</literal> content. The content URI - identifies which content to be displayed, in this case, the <literal>HelloWorldPortletInstance</literal>. - It is possible to declare windows with a <literal>cms</literal> content type and use directly the path to - the file in the CMS to make the window show the content of the associated file. That behavior is - pluggable and it is possible to plug virtually any kind of content. - </para> + This is equivalent to the previous <filename>HelloWorldPortlet/WEB-INF/helloworld-object.xml</filename> example. The content to be display can be specified using <computeroutput>&lt;content-type&gt;</computeroutput>. In this example, the content being displayed is a portlet. The <computeroutput>&lt;content-uri&gt;</computeroutput> specifies which content to display, in this case, the <computeroutput>HelloWorldPortletInstance</computeroutput>: + </para> + <para> +<screen><![CDATA[ +<content> + <content-type>portlet</content-type> + <content-uri>HelloWorldPortletInstance</content-uri> +</content>]]> +</screen> + </para> + <para> + To display certain content or a file, use the <computeroutput>cms</computeroutput> content-type, with the <computeroutput>&lt;content-uri&gt;</computeroutput> being the path to the file in the CMS. This behavior is pluggable, and it is possible to plug almost any kind of content. + </para> </sect3> <sect3 id="first_portlet_build"> <title>Building your portlet</title>