From portal-commits at lists.jboss.org Fri Jul 18 12:28:33 2008
Content-Type: multipart/mixed; boundary="===============5643001318789069221=="
MIME-Version: 1.0
From: portal-commits at lists.jboss.org
To: portal-commits at lists.jboss.org
Subject: [portal-commits] JBoss Portal SVN: r11502 -
 docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
Date: Fri, 18 Jul 2008 12:28:33 -0400
Message-ID: <E1KJsor-0002Y6-FM@committer01.frg.pub.inap.atl.jboss.com>

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

Author: chris.laprun(a)jboss.com
Date: 2008-07-18 12:28:33 -0400 (Fri, 18 Jul 2008)
New Revision: 11502

Modified:
   docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/wsrp.xml
Log:
- Added documentation on WSRP validation mode.

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	2008-07-18 15:30:25 UTC (rev 11501)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/wsrp.xm=
l	2008-07-18 16:28:33 UTC (rev 11502)
@@ -956,5 +956,39 @@
             </para>
          </sect3>
       </sect2>
+      <sect2 id=3D"strict-mode">
+         <title>WSRP validation mode</title>
+         <para>The lack of conformance kit and the wording of the WSRP spe=
cification leaves room for differing
+            interpretations, resulting in interoperability issues. It is t=
herefore possible to encounter issues when
+            using consumers from different vendors. We have experienced su=
ch issues and have introduced a way to relax
+            the validation that our WSRP producer performs on the data pro=
vided by consumers to help with
+            interoperability by accepting data that would normally be inva=
lid. Note that we only relax our validation
+            algorithm on aspects of the specification that are deemed harm=
less such as invalid language codes.
+         </para>
+         <para>
+            By default, the WSRP producer is configured in strict mode. If=
 you experience issues with a given consumer,
+            you might want to try to relax the validation mode. This is ac=
complished by editing
+            <filename>jboss-portal.sar/portal-wsrp.sar/META-INF/jboss-serv=
ice.xml</filename> and setting the value of
+            the <literal>UseStrictMode</literal> attribute to <literal>fal=
se</literal> as shown below:
+
+            <programlisting><![CDATA[
+<!-- WSRP Producer implementation -->
+<mbean code=3D"org.jboss.portal.wsrp.producer.WSRPProducerImpl"
+       name=3D"portal.wsrp:service=3DWSRPProducer"
+       xmbean-dd=3D""
+       xmbean-code=3D"org.jboss.portal.jems.as.system.JBossServiceModelMBe=
an">
+   <xmbean/>
+   <depends optional-attribute-name=3D"Invoker" proxy-type=3D"attribute">p=
ortal:service=3DPortletInvoker,type=3DProducer
+   </depends>
+   <depends optional-attribute-name=3D"RegistrationManager" proxy-type=3D"=
attribute">
+      portal.wsrp:service=3DRegistrationManager,type=3DProducer
+   </depends>
+   <depends optional-attribute-name=3D"ProducerConfigurationService" proxy=
-type=3D"attribute">
+      portal.wsrp:service=3DProducerConfiguration
+   </depends>
+   <attribute name=3D"UseStrictMode">true</attribute><!-- Set to false to =
switch to lenient mode -->
+</mbean>]]></programlisting>
+         </para>
+      </sect2>
    </sect1>
 </chapter>


--===============5643001318789069221==--