cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r818160 - in /websites/production/cxf/content: cache/docs.pageCache docs/jax-rs-redirection.html docs/jax-rs-xml-security.html
Date Fri, 18 May 2012 11:48:39 GMT
Author: buildbot
Date: Fri May 18 11:48:39 2012
New Revision: 818160

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/jax-rs-redirection.html
    websites/production/cxf/content/docs/jax-rs-xml-security.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/jax-rs-redirection.html
==============================================================================
--- websites/production/cxf/content/docs/jax-rs-redirection.html (original)
+++ websites/production/cxf/content/docs/jax-rs-redirection.html Fri May 18 11:48:39 2012
@@ -235,6 +235,19 @@ Note that RequestDispatcherProvider can 
 <p>Note that RequestDispatcherProvider has a 'dispatcherName' property - that can be
handy when redirecting to named servlets (example, MyServlet) including<br clear="none">
 such ones as "jsp" or "default", especially when CXFServlet handling a given invocation has
a uri pattern that may also capture the redirection requestwell-known servlets such as "default",
see the next section for more information. </p>
 
+<p>Starting from CXF 2.6.1 it is possible to configure the provider to check if the
current class has an associated view handler or not, for example:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;bean id=<span class="code-quote">"viewHandler"</span>
class=<span class="code-quote">"org.apache.cxf.jaxrs.provider.RequestDispatcherProvider"</span>&gt;</span>
+         <span class="code-tag">&lt;property name=<span class="code-quote">"dispatcherName"</span>
value=jsp""/&gt;</span>
+         <span class="code-tag">&lt;property name=<span class="code-quote">"useClassNames"</span>
value=<span class="code-quote">"true"</span>/&gt;</span>
+<span class="code-tag">&lt;/bean&gt;</span>
+</pre>
+</div></div>
+
+<p>For example, given a simple class name such as "BookInfo", RequestDispatcherProvider
will check if a "/WEB-INF/bookInfo.jsp" handler is available or not. The provider will likely
be extended to check few more locations as needed.  </p>
+
 <p>Finally, a 'servletContextPath' property can be used to have some other ServletContext
(as opposed to the current one) be used for RequestDispatcher look-ups. If set then the current
ServletContext.getContext(servletContextPath) will be used to get the needed ServletContext.</p>
 
 <h1><a shape="rect" name="JAX-RSRedirection-WithCXFServlet"></a>With CXFServlet</h1>

Modified: websites/production/cxf/content/docs/jax-rs-xml-security.html
==============================================================================
--- websites/production/cxf/content/docs/jax-rs-xml-security.html (original)
+++ websites/production/cxf/content/docs/jax-rs-xml-security.html Fri May 18 11:48:39 2012
@@ -657,9 +657,21 @@ The following properties can be set on i
     <span class="code-tag">&lt;bean id=<span class="code-quote">"xmlEncInHandlerWithProps"</span>
class=<span class="code-quote">"org.apache.cxf.rs.security.xml.XmlEncInHandler"</span>&gt;</span>
         <span class="code-tag">&lt;property name=<span class="code-quote">"encryptionProperties"</span>
ref=<span class="code-quote">"encProps"</span>/&gt;</span>
     <span class="code-tag">&lt;/bean&gt;</span>
+
+    <span class="code-tag"><span class="code-comment">&lt;!-- the following
ensures that the outbound handlers will use the same algorithms that the client used --&gt;</span></span>
 
+    <span class="code-tag">&lt;bean id=<span class="code-quote">"xmlSigOutHandlerWithProps"</span>
class=<span class="code-quote">"org.apache.cxf.rs.security.xml.XmlSigOutInterceptor"</span>&gt;</span>
+        <span class="code-tag">&lt;property name=<span class="code-quote">"signatureProperties"</span>
ref=<span class="code-quote">"sigProps"</span>/&gt;</span>
+    <span class="code-tag">&lt;/bean&gt;</span>
+        
+    <span class="code-tag">&lt;bean id=<span class="code-quote">"xmlEncOutHandlerWithProps"</span>
class=<span class="code-quote">"org.apache.cxf.rs.security.xml.XmlEncOutInterceptor"</span>&gt;</span>
+        <span class="code-tag">&lt;property name=<span class="code-quote">"encryptionProperties"</span>
ref=<span class="code-quote">"encProps"</span>/&gt;</span>
+    <span class="code-tag">&lt;/bean&gt;</span>
 </pre>
 </div></div>
 
+<p>Getting the same SignatureProperties and EncryptionProperties beans (with "sigProps"
and "encProps" ids) registered with the outbound<br clear="none">
+handlers will ensure that the algorithms used by the current client have not only been validated
on the inbound side but also used on the outbound side for encrypting and signing the data.</p>
+
 <h1><a shape="rect" name="JAX-RSXMLSecurity-Interoperability"></a>Interoperability</h1>
 
 <p>The payloads containing the enveloping XML Signatures are structured according to
the XML Signature specification and as such can be consumed by any XML Signature aware consumers
capable of handling the enveloping signatures and extracting the signed payload. </p>



Mime
View raw message