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 5AE6217CF0 for ; Tue, 14 Apr 2015 22:47:19 +0000 (UTC) Received: (qmail 31573 invoked by uid 500); 14 Apr 2015 22:47:19 -0000 Delivered-To: apmail-cxf-commits-archive@cxf.apache.org Received: (qmail 31518 invoked by uid 500); 14 Apr 2015 22:47:19 -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 31509 invoked by uid 99); 14 Apr 2015 22:47:19 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Apr 2015 22:47:19 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id 0D504AC0113 for ; Tue, 14 Apr 2015 22:47:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r947659 - in /websites/production/cxf/content: cache/docs.pageCache docs/jax-rs-deployment.html Date: Tue, 14 Apr 2015 22:47:18 -0000 To: commits@cxf.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150414224719.0D504AC0113@hades.apache.org> Author: buildbot Date: Tue Apr 14 22:47:18 2015 New Revision: 947659 Log: Production update by buildbot for cxf Modified: websites/production/cxf/content/cache/docs.pageCache websites/production/cxf/content/docs/jax-rs-deployment.html Modified: websites/production/cxf/content/cache/docs.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/cxf/content/docs/jax-rs-deployment.html ============================================================================== --- websites/production/cxf/content/docs/jax-rs-deployment.html (original) +++ websites/production/cxf/content/docs/jax-rs-deployment.html Tue Apr 14 22:47:18 2015 @@ -116,100 +116,34 @@ Apache CXF -- JAX-RS Deployment
-

JAX-RS : Deployment

+

 

 

 

 

 JAX-RS : Deployment 

 

 

 

 

+/*]]>*/

- -

This page provides the tips on how to deploy CXF JAX-RS applications packaged as WAR archives or OSGI bundles into Java EE application servers and OSGI containers.

- -

Servlet Containers

-

Tomcat

-

1. System "org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH"
-and "org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH" properties may have to be set to "true" to support URIs containing encoded forward or backward slashes.
-2. When using mod_jk - ensure that the JkOptions setting has +ForwardURICompatUnparsed set.
-3. Windows: upgrade isapi_redirect.dll if you see URI containing encoded spaces being decoded by Tomcat.

- -

Application Servers

-

Glassfish

- -

Verified with Glassfish Server Open Source Edition 3.1.1

- -

1. Make sure a cxf-rt-transport-http-jetty dependency is excluded during the war build

- -

2. If a custom JAX-RS Application is included then
-use a CXFNonSpringJaxrsServlet to reference the Application implementation class and either
- 2.1 Disable the Jersey scanning the custom web applications. Setting the following system property may help:
- "-Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext"

- -

2.2 Remove jersey-gf-server.jar from $GLASSFISH_HOME/glassfish/modules

- -

JBoss

- -

Verified with JBoss AS 7.1.0.CR1b

- -

1. If a custom JAX-RS Application is included then
-use a CXFNonSpringJaxrsServlet to reference the Application implementation class and either

- -

1.1 Disable the RestEasy scanning the custom web applications (TODO: specify how this actually can be done)
- 1.2 Modify $JBOSS_HOME/standalone/configuration/standalone.xml by commenting out a "org.jboss.as.jaxrs" extension and a "urn:jboss:domain:jaxrs:1.0" sybsystem.

- -

2. JBoss does not support URI path slashes by default: http://securitytracker.com/id/1018110

- -

WebLogic

- -

Verified with WebLogic Server 12c (12.1.1)

- -

Specifying a WebLogic specific JSP servlet

- -

If you configure CXFServlet to redirect to custom JSP pages then you need to add the following declaration to web.xml:

-
- -
- -

CXF RuntimeDelegate

- -

Add a "prefer-application-packages" block in weblogic.xml, including the package "javax.ws.rs.*", for CXF RuntimeDelegate be visible after the application has been redeployed

- -

Selecting Woodstox as the default parser

- -

WebLogic requires the following update to the proprietary deployment descriptor weblogic.xml:

-
- -
- -

This instructs WebLogic's classloaders to look FIRST in the JARS from the application's WEB-INF/lib directory for Service Provider Implementations (in this case, to find META-INF/services/javax.xml.stream.XMLInputFactory in the Woodstox JAR) rather than to the system classloader.
-Please see this thread for more information.

- -

Geronimo

- -

CXF RuntimeDelegate

- -

It has been reported CXF RuntimeDelegate may not be visible after the application has been redeployed in Geronimo. Most likely Geronimo needs to be configured similar to the way WebLogic has to to resolve the same issue (please see the relevant section above), TODO: update the section once we know the actual details.

+

This instructs WebLogic's classloaders to look FIRST in the JARS from the application's WEB-INF/lib directory for Service Provider Implementations (in this case, to find META-INF/services/javax.xml.stream.XMLInputFactory in the Woodstox JAR) rather than to the system classloader.
Please see this thread for more information.

How to use CXF JAX-RS 2.0 if WebLogic ships JAX-RS 1.1

Please see the following email message.

Geronimo

CXF RuntimeDelegate

It has been reported CXF RuntimeDelegate may no t be visible after the application has been redeployed in Geronimo. Most likely Geronimo needs to be configured similar to the way WebLogic has to to resolve the same issue (please see the relevant section above), TODO: update the section once we know the actual details.