From portal-commits at lists.jboss.org Mon Mar 31 23:44:57 2008
Content-Type: multipart/mixed; boundary="===============1441756669322071642=="
MIME-Version: 1.0
From: portal-commits at lists.jboss.org
To: portal-commits at lists.jboss.org
Subject: [portal-commits] JBoss Portal SVN: r10442 -
 docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
Date: Mon, 31 Mar 2008 22:57:23 -0400
Message-ID: <E1JgWgd-0002lV-MX@committer01.frg.pub.inap.atl.jboss.com>

--===============1441756669322071642==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: mmcallis
Date: 2008-03-31 22:57:23 -0400 (Mon, 31 Mar 2008)
New Revision: 10442

Modified:
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescr=
iptors.xml
Log:
6.2.4. The portlet.xml Descriptor
- revising text
- periodic backup


Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/x=
mldescriptors.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldesc=
riptors.xml	2008-04-01 00:57:20 UTC (rev 10441)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldesc=
riptors.xml	2008-04-01 02:57:23 UTC (rev 10442)
@@ -1391,10 +1391,10 @@
       <sect2>
          <title>The <filename>portlet.xml</filename> Descriptor</title>
          <para>
-		 The <filename>portlet.xml</filename> descriptor is the standard portlet=
 descriptor covered by the <ulink url=3D"http://www.jcp.org/en/jsr/detail?i=
d=3D168">JSR-168 Portlet Specification</ulink>. Developers are strongly enc=
ouraged to read the <ulink url=3D"http://www.jcp.org/en/jsr/detail?id=3D168=
">JSR-168 Portlet Specification</ulink> items covering the correct use of t=
his descriptor, as it is oinly covered briefly in this section. Normally, t=
he <filename>portlet.xml</filename> descriptor is packaged inside your port=
let WAR file, alongside other the other descriptors in these sections. The =
following example is a modified version of the JBoss Portal UserPortlet def=
inition:
+		 The <filename>portlet.xml</filename> descriptor is the standard portlet=
 descriptor covered by the <ulink url=3D"http://www.jcp.org/en/jsr/detail?i=
d=3D168">JSR-168 Portlet Specification</ulink>. Developers are strongly enc=
ouraged to read the <ulink url=3D"http://www.jcp.org/en/jsr/detail?id=3D168=
">JSR-168 Portlet Specification</ulink> items covering the correct use of t=
his descriptor, as it is only covered briefly in these sections. Normally, =
the <filename>portlet.xml</filename> descriptor is packaged inside your por=
tlet WAR file, alongside the other descriptors in these sections. The follo=
wing example is a modified version of the JBoss Portal UserPortlet definiti=
on:
 	 </para>
 	 <para>
-            <programlisting><![CDATA[
+<screen><![CDATA[
 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
 <portlet-app
       xmlns=3D"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd"
@@ -1425,39 +1425,49 @@
          <title>User portlet</title>
       </portlet-info>
    </portlet>
-</portlet-app>
-]]></programlisting>
+</portlet-app>]]>
+</screen>
+	</para>
+	<para>
             <itemizedlist>
                <listitem>
                   <para>
                      <programlisting><![CDATA[<portlet-app>...</portlet-ap=
p>]]></programlisting>
-                     The <emphasis>portlet-app</emphasis> tag, encapsulate=
s the entire document. You may specify more
-                     than one portlet, within this tag.
+	     	   </para>
+		   <para>
+			   The <computeroutput>&lt;portlet-app&gt;</computeroutput> element enc=
apsulates the entire document. Multiple portlets can be specified using the=
 <computeroutput>&lt;portlet-app&gt;</computeroutput> element.
                   </para>
                </listitem>
                <listitem>
                   <para>
                      <programlisting><![CDATA[<portlet>...</portlet>]]></p=
rogramlisting>
-                     The <emphasis>portlet</emphasis> tag is used to defin=
e one portlet that is deployed within
-                     this archive.
+	     	 </para>
+		 <para>
+                     The <computeroutput>&lt;portlet&gt;</computeroutput> =
element defines one portlet that is deployed within this archive.
                   </para>
                </listitem>
                <listitem>
                   <para>
                      <programlisting><![CDATA[<description>...</descriptio=
n>]]></programlisting>
-                     A verbal description of this portlet's function.
+	          </para>
+		  <para>
+			  The <computeroutput>&lt;description&gt;</computeroutput> element is a=
 verbal description of the portlet's function.
                   </para>
                </listitem>
                <listitem>
                   <para>
                      <programlisting><![CDATA[<portlet-name>...</portlet-n=
ame>]]></programlisting>
-                     The name of this portlet, usually the class name, tho=
ugh it doesn't have to be.
+	     	  </para>
+		  <para>
+			  The <computeroutput>&lt;portlet-name&gt;</computeroutput> element def=
ines the portlet name. It does not have to be the class name.
                   </para>
                </listitem>
                <listitem>
                   <para>
                      <programlisting><![CDATA[<portlet-class>...</portlet-=
class>]]></programlisting>
-                     The fully-qualified name of this portlet class.
+	          </para>
+		  <para>
+			  The <computeroutput>&lt;portlet-class&gt;</computeroutput> element de=
fines the Fully Qualified Name (FQN) of the portlet class.
                   </para>
                </listitem>
                <listitem>


--===============1441756669322071642==--