Return-Path: X-Original-To: apmail-cxf-commits-archive@www.apache.org Delivered-To: apmail-cxf-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD05F9709 for ; Fri, 18 May 2012 11:49:10 +0000 (UTC) Received: (qmail 52311 invoked by uid 500); 18 May 2012 11:49:07 -0000 Delivered-To: apmail-cxf-commits-archive@cxf.apache.org Received: (qmail 52163 invoked by uid 500); 18 May 2012 11:49:05 -0000 Mailing-List: contact commits-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list commits@cxf.apache.org Received: (qmail 52133 invoked by uid 99); 18 May 2012 11:49:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2012 11:49:04 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2012 11:49:01 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 0E8532388865 for ; Fri, 18 May 2012 11:48:40 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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 -0000 To: commits@cxf.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120518114840.0E8532388865@eris.apache.org> 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

Note that RequestDispatcherProvider has a 'dispatcherName' property - that can be handy when redirecting to named servlets (example, MyServlet) including
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.

+

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:

+ +
+
+<bean id="viewHandler" class="org.apache.cxf.jaxrs.provider.RequestDispatcherProvider">
+         <property name="dispatcherName" value=jsp""/>
+         <property name="useClassNames" value="true"/>
+</bean>
+
+
+ +

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.

+

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.

With CXFServlet

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 <bean id="xmlEncInHandlerWithProps" class="org.apache.cxf.rs.security.xml.XmlEncInHandler"> <property name="encryptionProperties" ref="encProps"/> </bean> + + <!-- the following ensures that the outbound handlers will use the same algorithms that the client used --> + <bean id="xmlSigOutHandlerWithProps" class="org.apache.cxf.rs.security.xml.XmlSigOutInterceptor"> + <property name="signatureProperties" ref="sigProps"/> + </bean> + + <bean id="xmlEncOutHandlerWithProps" class="org.apache.cxf.rs.security.xml.XmlEncOutInterceptor"> + <property name="encryptionProperties" ref="encProps"/> + </bean> +

Getting the same SignatureProperties and EncryptionProperties beans (with "sigProps" and "encProps" ids) registered with the outbound
+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.

+

Interoperability

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.