From portal-commits at lists.jboss.org Fri Oct 12 21:34:15 2007
Content-Type: multipart/mixed; boundary="===============0114596667144676299=="
MIME-Version: 1.0
From: portal-commits at lists.jboss.org
To: portal-commits at lists.jboss.org
Subject: [portal-commits] JBoss Portal SVN: r8626 - in docs:
 branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules and 2 other
 directories.
Date: Fri, 12 Oct 2007 21:34:14 -0400
Message-ID: <E1IgVtO-0004do-NV@committer01.frg.pub.inap.atl.jboss.com>

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

Author: chris.laprun(a)jboss.com
Date: 2007-10-12 21:34:14 -0400 (Fri, 12 Oct 2007)
New Revision: 8626

Modified:
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/errorhand=
ling/errorHandlingUI.png
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorhan=
dling.xml
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/wsrp.xml
   docs/trunk/referenceGuide/en/images/errorhandling/errorHandlingUI.png
   docs/trunk/referenceGuide/en/modules/errorhandling.xml
   docs/trunk/referenceGuide/en/modules/wsrp.xml
Log:
- Minor content improvements.
- Updated error handling screenshot to be less wide.

Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/er=
rorhandling/errorHandlingUI.png
=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
(Binary files differ)

Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/e=
rrorhandling.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/errorha=
ndling.xml	2007-10-13 00:08:20 UTC (rev 8625)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/errorha=
ndling.xml	2007-10-13 01:34:14 UTC (rev 8626)
@@ -8,18 +8,19 @@
       </author>
    </chapterinfo>
    <title>Error handling configuration</title>
-   <para>JBoss Portal request pipeline provides configuring of the error h=
andling policy. At runtime when an error
-   occurs it is possible to configure how the portal behaves in a fine gra=
ined and dynamic manner.</para>
+   <para>JBoss Portal's request pipeline allows for fine-grained, dynamic =
configuration of how Portal will behave when
+      an error occurs at runtime.</para>
    <sect1>
       <title>Error types</title>
-      <para>There are several kind of errors that can be happen during a r=
equest.</para>
-      <itemizedlist>
-         <listitem>Access denied: the user does not have the security righ=
ts to access a resource</listitem>
-         <listitem>Error: an expected error, like a portlet threw an excep=
tion</listitem>
-         <listitem>Internal error: an unexpected error</listitem>
-         <listitem>Resource not found: a resource is not found</listitem>
-         <listitem>Resource not available: a resource is found but is not =
serviceable</listitem>
-      </itemizedlist>
+      <para>There are several kind of errors that can happen during a requ=
est:
+         <itemizedlist>
+            <listitem>Access denied: the user does not have the security r=
ights to access a resource</listitem>
+            <listitem>Error: an anticipated error as when a portlet throws=
 an exception</listitem>
+            <listitem>Internal error: an unexpected error</listitem>
+            <listitem>Resource not found: a resource is not found</listite=
m>
+            <listitem>Resource not available: a resource is found but is n=
ot serviceable</listitem>
+         </itemizedlist>
+      </para>
    </sect1>
    <sect1>
       <title>Control policies</title>
@@ -28,29 +29,30 @@
       <sect2>
          <title>Policy delegation and cascading</title>
          <para>Whenever a control policy is invoked it is given the opport=
unity to change the response sent
-         by the control flow. If the control policy ignores the error then=
 the next policy will handle the error
-         at this turn. However if the control policy decides to provide a =
new response then the next policy
-         will not be invoked since the new response will not be of type er=
ror. For instance, if a portlet part of a page
-         produces an exception, the following reactions are possible:</par=
a>
-         <itemizedlist>
-            <listitem>The error is displayed in the window</listitem>
-            <listitem>The window is removed from the aggregation</listitem>
-            <listitem>An portal error page is displayed</listitem>
-            <listitem>An HTTP 500 error response is sent to the browser</l=
istitem>
-         </itemizedlist>
+            by the control flow. If the control policy ignores the error t=
hen the next policy will handle the error
+            at this turn. However if the control policy decides to provide=
 a new response then the next policy
+            will not be invoked since the new response will not be of type=
 error. For instance, if a portlet part of a
+            page produces an exception, the following reactions are possib=
le:
+            <itemizedlist>
+               <listitem>The error is displayed in the window</listitem>
+               <listitem>The window is removed from the aggregation</listi=
tem>
+               <listitem>An portal error page is displayed</listitem>
+               <listitem>An HTTP 500 error response is sent to the browser=
</listitem>
+            </itemizedlist>
+         </para>
       </sect2>
       <sect2>
          <title>Default policy</title>
          <para>The default policy applies when error are not handled at ot=
her level. By default errors are translated
             into the most appropriate HTTP response:
+            <itemizedlist>
+               <listitem>Access denied: HTTP 403 Forbidden response</listi=
tem>
+               <listitem>Error: HTTP 500 Internal Server Error response</l=
istitem>
+               <listitem>Internal error: HTTP 500 Internal Server Error re=
sponse</listitem>
+               <listitem>Resource not found: HTTP 404 Not Found response</=
listitem>
+               <listitem>Resource not available: HTTP 404 Not Found respon=
se</listitem>
+            </itemizedlist>
          </para>
-         <itemizedlist>
-            <listitem>Access denied: HTTP 403 Forbidden response</listitem>
-            <listitem>Error: HTTP 500 Internal Server Error response</list=
item>
-            <listitem>Internal error: HTTP 500 Internal Server Error respo=
nse</listitem>
-            <listitem>Resource not found: HTTP 404 Not Found response</lis=
titem>
-            <listitem>Resource not available: HTTP 404 Not Found response<=
/listitem>
-         </itemizedlist>
       </sect2>
       <sect2>
          <title>Portal policy</title>
@@ -61,14 +63,15 @@
       </sect2>
       <sect2>
          <title>Page policy</title>
-         <para>Window error policy controls how the page reacts to aggrega=
tion errors. Indeed the page is most of the time
-         an aggregation of several portlet windows and the action to take =
when an error occurs is different than the other
-         policies. Whenever an error occurs, the policy can either handle =
it or ignore it. If the error is ignored then
-         it will be treated by the portal policy. The different actions th=
at are possible upon an error are:</para>
-         <itemizedlist>
-            <listitem>Remove the window from the aggregation</listitem>
-            <listitem>Replace the markup of the window by a redirection to=
 a JSP page</listitem>
-         </itemizedlist>
+         <para>Window error policy controls how the page reacts to aggrega=
tion errors. Indeed the page is most of the
+            time an aggregation of several portlet windows and the action =
to take when an error occurs is different than
+            the other policies. Whenever an error occurs, the policy can e=
ither handle it or ignore it. If the error is
+            ignored then it will be treated by the portal policy. The diff=
erent actions that are possible upon an error are:
+            <itemizedlist>
+               <listitem>Remove the window from the aggregation</listitem>
+               <listitem>Replace the markup of the window by a redirection=
 to a JSP page</listitem>
+            </itemizedlist>
+         </para>
       </sect2>
    </sect1>
    <sect1>
@@ -310,11 +313,10 @@
          clicking on the Properties link on each of these pages. You can a=
lso specify how dashboards should behave with
          respect to error handling by clicking on the Dashboards tab of th=
e Portal management application.
       </para>
-      <para>Screenshot:</para>
-      <para>
-      	<imageobject>
-        	<imagedata fileref=3D"images/errorhandling/errorHandlingUI.png" f=
ormat=3D"png"/>
-        </imageobject>
+      <para>Screenshot:
+         <imageobject>
+            <imagedata fileref=3D"images/errorhandling/errorHandlingUI.png=
" format=3D"png" align=3D"center"/>
+         </imageobject>
       </para>
    </sect1>
 </chapter>
\ No newline at end of file

Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/w=
srp.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/wsrp.xm=
l	2007-10-13 00:08:20 UTC (rev 8625)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/wsrp.xm=
l	2007-10-13 01:34:14 UTC (rev 8626)
@@ -70,7 +70,7 @@
       <para>
          JBoss Portal provides a complete support of WSRP 1.0 standard int=
erfaces and offers
          both consumer and producer services. WSRP support is provided by =
the <emphasis>portal-wsrp.sar</emphasis>
-         service archive, included in the main <emphasis>jboss-portal.sar<=
/emphasis> service archive, if you've =

+         service archive, included in the main <emphasis>jboss-portal.sar<=
/emphasis> service archive, if you've
          obtained JBoss Portal from a binary distribution. If you don't in=
tend on using WSRP, we recommend that you
          remove the <emphasis>portal-wspr.sar</emphasis> from the main <em=
phasis>jboss-portal.sar</emphasis> service
          archive.</para>
@@ -337,35 +337,35 @@
                Let's now look at the Admin page and the Management portlet=
. Click on the "Portlet definitions" tab at the
                top. Once this is done, look at the list of available portl=
et providers. If all went well,
                you should see something similar to this:
-            <mediaobject>
-               <imageobject>
-                  <imagedata fileref=3D"images/wsrp/portlets.png" format=
=3D"png" align=3D"center" valign=3D"middle"/>
-               </imageobject>
-            </mediaobject>
-         </para>
-         <para>
-            We have 3 available portlet providers: <emphasis>local, self</=
emphasis> and <emphasis>bea</emphasis>. The
-            "local" portlet provider exposes all the portlets deployed in =
this particular instance of Portal. As
-            explained above, the "self" provider refers to the default WSR=
P consumer bundled with Portal that consumes
-            the portlets exposed by the default WSRP producer. The "bea" p=
rovider corresponds to BEA's public producer
-            we just configured. Select it and click on "Change". You shoul=
d now see something similar to:
-            <mediaobject>
-               <imageobject>
-                  <imagedata fileref=3D"images/wsrp/bea.png" format=3D"png=
" align=3D"center" valign=3D"middle"/>
-               </imageobject>
-            </mediaobject>
-         </para>
-         <para>
-            From there on out, you should be able to configure WSRP portle=
ts just as any other. In particular, you
-			can create an instance of one of the remote portlets offered by BEA's p=
ublic producer just like you would
-			create an instance of a local portlet and then assign it to a window in=
 a page. If you go to that page, you
-            should see something similar to below for this portlet:
-            <mediaobject>
-               <imageobject>
-                  <imagedata fileref=3D"images/wsrp/result.png" format=3D"=
png" align=3D"center" valign=3D"middle"/>
-               </imageobject>
-            </mediaobject>
-         </para>
+               <mediaobject>
+                  <imageobject>
+                     <imagedata fileref=3D"images/wsrp/portlets.png" forma=
t=3D"png" align=3D"center" valign=3D"middle"/>
+                  </imageobject>
+               </mediaobject>
+            </para>
+            <para>
+               We have 3 available portlet providers: <emphasis>local, sel=
f</emphasis> and <emphasis>bea</emphasis>. The
+               "local" portlet provider exposes all the portlets deployed =
in this particular instance of Portal. As
+               explained above, the "self" provider refers to the default =
WSRP consumer bundled with Portal that consumes
+               the portlets exposed by the default WSRP producer. The "bea=
" provider corresponds to BEA's public producer
+               we just configured. Select it and click on "Change". You sh=
ould now see something similar to:
+               <mediaobject>
+                  <imageobject>
+                     <imagedata fileref=3D"images/wsrp/bea.png" format=3D"=
png" align=3D"center" valign=3D"middle"/>
+                  </imageobject>
+               </mediaobject>
+            </para>
+            <para>
+               From there on out, you should be able to configure WSRP por=
tlets just as any other. In particular, you
+               can create an instance of one of the remote portlets offere=
d by BEA's public producer just like you would
+               create an instance of a local portlet and then assign it to=
 a window in a page. If you go to that page, you
+               should see something similar to below for this portlet:
+               <mediaobject>
+                  <imageobject>
+                     <imagedata fileref=3D"images/wsrp/result.png" format=
=3D"png" align=3D"center" valign=3D"middle"/>
+                  </imageobject>
+               </mediaobject>
+            </para>
          </sect3>
       </sect2>
 =

@@ -487,7 +487,7 @@
 =

          <para>
             <programlisting><![CDATA[
-<?xml version=3D"1.0" encoding=3D"UTF-8"?>            =

+<?xml version=3D"1.0" encoding=3D"UTF-8"?>
 <!DOCTYPE deployments PUBLIC "-//JBoss Portal//DTD WSRP Remote Producer Co=
nfiguration 2.6//EN"
    "http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd">
 =

@@ -526,7 +526,7 @@
 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
 <!DOCTYPE deployments PUBLIC "-//JBoss Portal//DTD WSRP Remote Producer Co=
nfiguration 2.6//EN"
    "http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd">
-      =

+
 <deployments>
    <deployment>
       <wsrp-producer id=3D"MyProducer" expiration-cache=3D"120">
@@ -557,7 +557,7 @@
 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
 <!DOCTYPE deployments PUBLIC "-//JBoss Portal//DTD WSRP Remote Producer Co=
nfiguration 2.6//EN"
    "http://www.jboss.org/portal/dtd/jboss-wsrp-consumer_2_6.dtd">
-   =

+
 <deployments>
    <deployment>
       <wsrp-producer id=3D"AnotherProducer" expiration-cache=3D"60">
@@ -702,7 +702,7 @@
 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
 <!DOCTYPE producer-configuration PUBLIC "-//JBoss Portal//DTD WSRP Local P=
roducer Configuration 2.6//EN"
    "http://www.jboss.org/portal/dtd/jboss-wsrp-producer_2_6.dtd">
-   =

+
 <producer-configuration>
   <registration-configuration fullServiceDescriptionRequiresRegistration=
=3D"true">
     <registration-policy>com.example.portal.SomeCustomRegistrationPolicy</=
registration-policy>

Modified: docs/trunk/referenceGuide/en/images/errorhandling/errorHandlingUI=
.png
=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
(Binary files differ)

Modified: docs/trunk/referenceGuide/en/modules/errorhandling.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/trunk/referenceGuide/en/modules/errorhandling.xml	2007-10-13 00:08=
:20 UTC (rev 8625)
+++ docs/trunk/referenceGuide/en/modules/errorhandling.xml	2007-10-13 01:34=
:14 UTC (rev 8626)
@@ -8,18 +8,19 @@
       </author>
    </chapterinfo>
    <title>Error handling configuration</title>
-   <para>JBoss Portal request pipeline provides configuring of the error h=
andling policy. At runtime when an error
-   occurs it is possible to configure how the portal behaves in a fine gra=
ined and dynamic manner.</para>
+   <para>JBoss Portal's request pipeline allows for fine-grained, dynamic =
configuration of how Portal will behave when
+      an error occurs at runtime.</para>
    <sect1>
       <title>Error types</title>
-      <para>There are several kind of errors that can be happen during a r=
equest.</para>
-      <itemizedlist>
-         <listitem>Access denied: the user does not have the security righ=
ts to access a resource</listitem>
-         <listitem>Error: an expected error, like a portlet threw an excep=
tion</listitem>
-         <listitem>Internal error: an unexpected error</listitem>
-         <listitem>Resource not found: a resource is not found</listitem>
-         <listitem>Resource not available: a resource is found but is not =
serviceable</listitem>
-      </itemizedlist>
+      <para>There are several kind of errors that can happen during a requ=
est:
+         <itemizedlist>
+            <listitem>Access denied: the user does not have the security r=
ights to access a resource</listitem>
+            <listitem>Error: an anticipated error as when a portlet throws=
 an exception</listitem>
+            <listitem>Internal error: an unexpected error</listitem>
+            <listitem>Resource not found: a resource is not found</listite=
m>
+            <listitem>Resource not available: a resource is found but is n=
ot serviceable</listitem>
+         </itemizedlist>
+      </para>
    </sect1>
    <sect1>
       <title>Control policies</title>
@@ -28,29 +29,30 @@
       <sect2>
          <title>Policy delegation and cascading</title>
          <para>Whenever a control policy is invoked it is given the opport=
unity to change the response sent
-         by the control flow. If the control policy ignores the error then=
 the next policy will handle the error
-         at this turn. However if the control policy decides to provide a =
new response then the next policy
-         will not be invoked since the new response will not be of type er=
ror. For instance, if a portlet part of a page
-         produces an exception, the following reactions are possible:</par=
a>
-         <itemizedlist>
-            <listitem>The error is displayed in the window</listitem>
-            <listitem>The window is removed from the aggregation</listitem>
-            <listitem>An portal error page is displayed</listitem>
-            <listitem>An HTTP 500 error response is sent to the browser</l=
istitem>
-         </itemizedlist>
+            by the control flow. If the control policy ignores the error t=
hen the next policy will handle the error
+            at this turn. However if the control policy decides to provide=
 a new response then the next policy
+            will not be invoked since the new response will not be of type=
 error. For instance, if a portlet part of a
+            page produces an exception, the following reactions are possib=
le:
+            <itemizedlist>
+               <listitem>The error is displayed in the window</listitem>
+               <listitem>The window is removed from the aggregation</listi=
tem>
+               <listitem>An portal error page is displayed</listitem>
+               <listitem>An HTTP 500 error response is sent to the browser=
</listitem>
+            </itemizedlist>
+         </para>
       </sect2>
       <sect2>
          <title>Default policy</title>
          <para>The default policy applies when error are not handled at ot=
her level. By default errors are translated
             into the most appropriate HTTP response:
+            <itemizedlist>
+               <listitem>Access denied: HTTP 403 Forbidden response</listi=
tem>
+               <listitem>Error: HTTP 500 Internal Server Error response</l=
istitem>
+               <listitem>Internal error: HTTP 500 Internal Server Error re=
sponse</listitem>
+               <listitem>Resource not found: HTTP 404 Not Found response</=
listitem>
+               <listitem>Resource not available: HTTP 404 Not Found respon=
se</listitem>
+            </itemizedlist>
          </para>
-         <itemizedlist>
-            <listitem>Access denied: HTTP 403 Forbidden response</listitem>
-            <listitem>Error: HTTP 500 Internal Server Error response</list=
item>
-            <listitem>Internal error: HTTP 500 Internal Server Error respo=
nse</listitem>
-            <listitem>Resource not found: HTTP 404 Not Found response</lis=
titem>
-            <listitem>Resource not available: HTTP 404 Not Found response<=
/listitem>
-         </itemizedlist>
       </sect2>
       <sect2>
          <title>Portal policy</title>
@@ -61,14 +63,15 @@
       </sect2>
       <sect2>
          <title>Page policy</title>
-         <para>Window error policy controls how the page reacts to aggrega=
tion errors. Indeed the page is most of the time
-         an aggregation of several portlet windows and the action to take =
when an error occurs is different than the other
-         policies. Whenever an error occurs, the policy can either handle =
it or ignore it. If the error is ignored then
-         it will be treated by the portal policy. The different actions th=
at are possible upon an error are:</para>
-         <itemizedlist>
-            <listitem>Remove the window from the aggregation</listitem>
-            <listitem>Replace the markup of the window by a redirection to=
 a JSP page</listitem>
-         </itemizedlist>
+         <para>Window error policy controls how the page reacts to aggrega=
tion errors. Indeed the page is most of the
+            time an aggregation of several portlet windows and the action =
to take when an error occurs is different than
+            the other policies. Whenever an error occurs, the policy can e=
ither handle it or ignore it. If the error is
+            ignored then it will be treated by the portal policy. The diff=
erent actions that are possible upon an error are:
+            <itemizedlist>
+               <listitem>Remove the window from the aggregation</listitem>
+               <listitem>Replace the markup of the window by a redirection=
 to a JSP page</listitem>
+            </itemizedlist>
+         </para>
       </sect2>
    </sect1>
    <sect1>
@@ -310,11 +313,10 @@
          clicking on the Properties link on each of these pages. You can a=
lso specify how dashboards should behave with
          respect to error handling by clicking on the Dashboards tab of th=
e Portal management application.
       </para>
-      <para>Screenshot:</para>
-      <para>
-      	<imageobject>
-        	<imagedata fileref=3D"images/errorhandling/errorHandlingUI.png" f=
ormat=3D"png"/>
-        </imageobject>
-      </para>
+      <para>Screenshot:
+         <imageobject>
+            <imagedata fileref=3D"images/errorhandling/errorHandlingUI.png=
" format=3D"png" align=3D"center"/>
+         </imageobject>
+      </para>      =

    </sect1>
 </chapter>
\ No newline at end of file

Modified: docs/trunk/referenceGuide/en/modules/wsrp.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/trunk/referenceGuide/en/modules/wsrp.xml	2007-10-13 00:08:20 UTC (=
rev 8625)
+++ docs/trunk/referenceGuide/en/modules/wsrp.xml	2007-10-13 01:34:14 UTC (=
rev 8626)
@@ -337,35 +337,35 @@
                Let's now look at the Admin page and the Management portlet=
. Click on the "Portlet definitions" tab at the
                top. Once this is done, look at the list of available portl=
et providers. If all went well,
                you should see something similar to this:
-            <mediaobject>
-               <imageobject>
-                  <imagedata fileref=3D"images/wsrp/portlets.png" format=
=3D"png" align=3D"center" valign=3D"middle"/>
-               </imageobject>
-            </mediaobject>
-         </para>
-         <para>
-            We have 3 available portlet providers: <emphasis>local, self</=
emphasis> and <emphasis>bea</emphasis>. The
-            "local" portlet provider exposes all the portlets deployed in =
this particular instance of Portal. As
-            explained above, the "self" provider refers to the default WSR=
P consumer bundled with Portal that consumes
-            the portlets exposed by the default WSRP producer. The "bea" p=
rovider corresponds to BEA's public producer
-            we just configured. Select it and click on "Change". You shoul=
d now see something similar to:
-            <mediaobject>
-               <imageobject>
-                  <imagedata fileref=3D"images/wsrp/bea.png" format=3D"png=
" align=3D"center" valign=3D"middle"/>
-               </imageobject>
-            </mediaobject>
-         </para>
-         <para>
-            From there on out, you should be able to configure WSRP portle=
ts just as any other. In particular, you
-			can create an instance of one of the remote portlets offered by BEA's p=
ublic producer just like you would
-			create an instance of a local portlet and then assign it to a window in=
 a page. If you go to that page, you
-            should see something similar to below for this portlet:
-            <mediaobject>
-               <imageobject>
-                  <imagedata fileref=3D"images/wsrp/result.png" format=3D"=
png" align=3D"center" valign=3D"middle"/>
-               </imageobject>
-            </mediaobject>
-         </para>
+               <mediaobject>
+                  <imageobject>
+                     <imagedata fileref=3D"images/wsrp/portlets.png" forma=
t=3D"png" align=3D"center" valign=3D"middle"/>
+                  </imageobject>
+               </mediaobject>
+            </para>
+            <para>
+               We have 3 available portlet providers: <emphasis>local, sel=
f</emphasis> and <emphasis>bea</emphasis>. The
+               "local" portlet provider exposes all the portlets deployed =
in this particular instance of Portal. As
+               explained above, the "self" provider refers to the default =
WSRP consumer bundled with Portal that consumes
+               the portlets exposed by the default WSRP producer. The "bea=
" provider corresponds to BEA's public producer
+               we just configured. Select it and click on "Change". You sh=
ould now see something similar to:
+               <mediaobject>
+                  <imageobject>
+                     <imagedata fileref=3D"images/wsrp/bea.png" format=3D"=
png" align=3D"center" valign=3D"middle"/>
+                  </imageobject>
+               </mediaobject>
+            </para>
+            <para>
+               From there on out, you should be able to configure WSRP por=
tlets just as any other. In particular, you
+               can create an instance of one of the remote portlets offere=
d by BEA's public producer just like you would
+               create an instance of a local portlet and then assign it to=
 a window in a page. If you go to that page, you
+               should see something similar to below for this portlet:
+               <mediaobject>
+                  <imageobject>
+                     <imagedata fileref=3D"images/wsrp/result.png" format=
=3D"png" align=3D"center" valign=3D"middle"/>
+                  </imageobject>
+               </mediaobject>
+            </para>
          </sect3>
       </sect2>
 =



--===============0114596667144676299==--