Author: mmcallis Date: 2008-02-19 02:47:47 -0500 (Tue, 19 Feb 2008) New Revision: 10024 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml Log: minor additions 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-19 04:56:52 UTC (rev 10023) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-19 07:47:47 UTC (rev 10024) @@ -316,7 +316,7 @@ </supports>]]></screen></term> <listitem> <para> - The <computeroutput>&lt;supports&gt;</computeroutput> element allows you to declare all of the markup types your portlet supports in the <literal>render</literal> method. This is accomplished via the + The <computeroutput>&lt;supports&gt;</computeroutput> element allows you to declare all of the markup types that your portlet supports in the <literal>render</literal> method. This is accomplished via the <computeroutput>&lt;mime-type&gt;</computeroutput> element, which is required for every portlet. The declared MIME types must match the capability of the portlet. As well, it allows you to pair which modes and window states are supported for each markup type. All portlets must support the VIEW portlet mode, so this does not have to be declared. Use the <computeroutput>&lt;mime-type&gt;</computeroutput> element to define which markup type your portlet supports, which in this example, is <computeroutput>text/html</computeroutput>. This section tells the portal that it will only output text and HTML, and that it only supports the <computeroutput>VIEW</computeroutput> mode. </para> </listitem> @@ -1091,7 +1091,7 @@ </supports>]]></screen></term> <listitem> <para> - The <computeroutput>&lt;supports&gt;</computeroutput> element allows you to declare all of the markup types your portlet supports in the <literal>render</literal> method. This is accomplished via the + The <computeroutput>&lt;supports&gt;</computeroutput> element allows you to declare all of the markup types that your portlet supports in the <literal>render</literal> method. This is accomplished via the <computeroutput>&lt;mime-type&gt;</computeroutput> element, which is required for every portlet. The declared MIME types must match the capability of the portlet. As well, it allows you to pair which modes and window states are supported for each markup type. All portlets must support the VIEW portlet mode, so this does not have to be declared. Use the <computeroutput>&lt;mime-type&gt;</computeroutput> element to define which markup type your portlet supports, which in this example, is <computeroutput>text/html</computeroutput>. This section tells the portal that it will only output text and HTML, and that it only supports the <computeroutput>VIEW</computeroutput> mode. </para> </listitem> @@ -1423,7 +1423,7 @@ </supports>]]></screen></term> <listitem> <para> - The <computeroutput>&lt;supports&gt;</computeroutput> element allows you to declare all of the markup types your portlet supports in the <literal>render</literal> method. This is accomplished via the + The <computeroutput>&lt;supports&gt;</computeroutput> element allows you to declare all of the markup types that your portlet supports in the <literal>render</literal> method. This is accomplished via the <computeroutput>&lt;mime-type&gt;</computeroutput> element, which is required for every portlet. The declared MIME types must match the capability of the portlet. As well, it allows you to pair which modes and window states are supported for each markup type. All portlets must support the VIEW portlet mode, so this does not have to be declared. Use the <computeroutput>&lt;mime-type&gt;</computeroutput> element to define which markup type your portlet supports, which in this example, is <computeroutput>text/html</computeroutput>. This section tells the portal that it will only output text and HTML, and that it only supports the <computeroutput>VIEW</computeroutput> mode. </para> </listitem> @@ -1434,7 +1434,7 @@ <note> <title>Adding Functionality to an Apache MyFaces JSF Portlet</title> <para> - To add functionality to an Apache MyFaces JSF Portlet, sub-class it and create your own class. + To add functionality to an Apache MyFaces JSF portlet, sub-class it and create your own class. </para> </note> </para> @@ -1479,7 +1479,7 @@ </screen> </para> <para> - These extra parameters let the application server know that the portlet embeds its own libraries. This avoids collision with the Sun JSF RI libraries bundled with JBoss AS and JBoss EAP. For more information, refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces">Ap... MyFaces page on the JBoss Wiki</ulink>. + These extra parameters let the application server know that the portlet embeds its own libraries. This avoids collision with the Sun JSF RI libraries bundled with JBoss AS and JBoss EAP. For more information, refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces">JB... page on the JBoss Wiki</ulink>. </para> </sect3> <sect3> @@ -1555,7 +1555,7 @@ <para> Performing this step on a running instance of JBoss AS or JBoss EAP, and JBoss Portal, will trigger a hot-deploy of the portlet. </para><para> - To see the HelloWorldJSFMyFaces42Portlet, navigate to <ulink url="http://localhost:8080/portal/"></ulink>, or, if the default JBoss Portal page is already open, refresh the page. HelloWorldJSFMyFaces42Portlet is added to the bottom of the default JBoss Portal page: + To see the HelloWorldJSFMyFaces42Portlet, navigate to <ulink url="http://localhost:8080/portal/"></ulink>, or, if the default JBoss Portal page is already open, refresh the page. The HelloWorldJSFMyFaces42Portlet is added to the bottom of the default JBoss Portal page: </para> <para> <mediaobject>