[jboss-cvs] JBossAS SVN: r105128 - projects/docs/enterprise/5.1/CXF_User_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: rebecca_newton
Date: 2010-05-24 01:18:27 -0400 (Mon, 24 May 2010)
New Revision: 105128

Modified:
   projects/docs/enterprise/5.1/CXF_User_Guide/en-US/Policy.xml
Log:
updating

Modified: projects/docs/enterprise/5.1/CXF_User_Guide/en-US/Policy.xml
===================================================================
--- projects/docs/enterprise/5.1/CXF_User_Guide/en-US/Policy.xml	2010-05-24 05:17:32 UTC (rev 105127)
+++ projects/docs/enterprise/5.1/CXF_User_Guide/en-US/Policy.xml	2010-05-24 05:18:27 UTC (rev 105128)
@@ -39,14 +39,14 @@
         <title> AssertionBuilder</title>
           <para> The AssertionBuilder <acronym>API</acronym> has been slightly modified from the original to avoid the dependency on the Axis object model, and extended to include support for domain specific behaviour of intersection and comparison.
           </para>
-          <programlisting language="Java" role="JAVA">
+          <programlisting language="Java" role="JAVA"><![CDATA[
         public interface AssertionBuilder {
    // build an Assertion object from a given DOM element
    Assertion build(Element element);
   // return the schema type names of assertions understood by this builder
   Collection<QName> getSupportedTypes();
   // return an Assertion object that is compatible with the specified assertions
-  Assertion buildCompatible(Assertion a, Assertion b);
+  Assertion buildCompatible(Assertion a, Assertion b);]]>
         </programlisting>
         <para> AsssertionBuilder implements are loaded dynamically and are automatically registered with the AssertionBuilderRegistry, which is available as a Bus extension. Currently, CXF supports <classname>AssertionBuilder</classname> and Assertion implementations for the following assertion types, along with the WS-SecurityPolicy defined assertions.
         </para>
@@ -70,7 +70,7 @@
             <para>{http://cxf.apache.org/transports/http/configuration}server</para>
           </listitem>
       </itemizedlist>
-           <para> They are all based on generic Assertion implementations (<classname>PrimitiveAssertion</classname>, </classname>NestedPrimitiveAssertion</classname>, and <classname>JaxbAssertion</classname>) that developers can define or extend when developing their own assertions.
+           <para> They are all based on generic Assertion implementations (<classname>PrimitiveAssertion</classname>, <classname>NestedPrimitiveAssertion</classname>, and <classname>JaxbAssertion</classname>) that developers can define or extend when developing their own assertions.
       </para>
     </section>
     <section>
@@ -138,7 +138,7 @@
         </para>
           <para> Their interaction with the policy framework therefore typically involves the <classname>PolicyEngine</classname> through which they obtain the effective policy for the underlying endpoints (for step one).
           </para>
-      <programlisting language="Java" role="JAVA">
+      <programlisting language="Java" role="JAVA"><![CDATA[
 public interface PolicyEngine {
     ...
     EndpointPolicy getClientEndpointPolicy(EndpointInfo ei, Conduit conduit);    
@@ -148,7 +148,7 @@
 public interface EndpointPolicy {
     ...
     Policy getPolicy(); 
-    Collection<Assertion> getChosenAlternative();
+    Collection<Assertion> getChosenAlternative();]]>
 }
      </programlisting>
       <para> To perform step two they implement the Assertor interface (namely its <methodname>assertMessage</methodname> method):