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
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><p></p><p></p><p></p><p></p><p><span 
class="inline-first-p" style="font-size:2em;font-weight:bold"> JAX-RS : 
Deployment </span></p><p></p><p></p><p></p><p></p><p></p>
+<div 
id="ConfluenceContent"><p>&#160;</p><p>&#160;</p><p>&#160;</p><p>&#160;</p><p>&#160;<span
 class="inline-first-p" style="font-size:2em;font-weight:bold">JAX-RS : 
Deployment</span>&#160;</p><p>&#160;</p><p>&#160;</p><p>&#160;</p><p>&#160;</p><p><style
 type="text/css">/*<![CDATA[*/
+div.rbtoc1429051602799 {padding: 0px;}
+div.rbtoc1429051602799 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1429051602799 li {margin-left: 0px;padding-left: 0px;}
 
-<style type="text/css">/*<![CDATA[*/
-div.rbtoc1419015906055 {padding: 0px;}
-div.rbtoc1419015906055 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1419015906055 li {margin-left: 0px;padding-left: 0px;}
-
-/*]]>*/</style><div class="toc-macro rbtoc1419015906055">
+/*]]>*/</style></p><div class="toc-macro rbtoc1429051602799">
 <ul class="toc-indentation"><li><a shape="rect" 
href="#JAX-RSDeployment-ServletContainers">Servlet Containers</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#JAX-RSDeployment-Tomcat">Tomcat</a></li></ul>
 </li><li><a shape="rect" 
href="#JAX-RSDeployment-ApplicationServers">Application Servers</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#JAX-RSDeployment-Glassfish">Glassfish</a></li><li><a shape="rect" 
href="#JAX-RSDeployment-JBoss">JBoss</a></li><li><a shape="rect" 
href="#JAX-RSDeployment-WebLogic">WebLogic</a>
-<ul class="toc-indentation"><li><a shape="rect" 
href="#JAX-RSDeployment-SpecifyingaWebLogicspecificJSPservlet">Specifying a 
WebLogic specific JSP servlet</a></li><li><a shape="rect" 
href="#JAX-RSDeployment-CXFRuntimeDelegate">CXF RuntimeDelegate</a></li><li><a 
shape="rect" 
href="#JAX-RSDeployment-SelectingWoodstoxasthedefaultparser">Selecting Woodstox 
as the default parser</a></li></ul>
+<ul class="toc-indentation"><li><a shape="rect" 
href="#JAX-RSDeployment-SpecifyingaWebLogicspecificJSPservlet">Specifying a 
WebLogic specific JSP servlet</a></li><li><a shape="rect" 
href="#JAX-RSDeployment-CXFRuntimeDelegate">CXF RuntimeDelegate</a></li><li><a 
shape="rect" 
href="#JAX-RSDeployment-SelectingWoodstoxasthedefaultparser">Selecting Woodstox 
as the default parser</a></li><li><a shape="rect" 
href="#JAX-RSDeployment-HowtouseCXFJAX-RS2.0ifWebLogicshipsJAX-RS1.1">How to 
use CXF JAX-RS 2.0 if WebLogic ships JAX-RS 1.1</a></li></ul>
 </li><li><a shape="rect" href="#JAX-RSDeployment-Geronimo">Geronimo</a>
 <ul class="toc-indentation"><li><a shape="rect" 
href="#JAX-RSDeployment-CXFRuntimeDelegate.1">CXF RuntimeDelegate</a></li></ul>
 </li></ul>
 </li></ul>
-</div>
-
-<p>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.  </p>
-
-<h1 id="JAX-RSDeployment-ServletContainers">Servlet Containers</h1>
-<h2 id="JAX-RSDeployment-Tomcat">Tomcat</h2>
-<p>1. System "org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH"<br 
clear="none">
-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.<br clear="none">
-2. When using mod_jk - ensure that the JkOptions setting has 
+ForwardURICompatUnparsed set. <br clear="none">
-3. Windows: upgrade isapi_redirect.dll if you see URI containing encoded 
spaces being decoded by Tomcat.</p>
-
-<h1 id="JAX-RSDeployment-ApplicationServers">Application Servers</h1>
-<h2 id="JAX-RSDeployment-Glassfish">Glassfish</h2>
-
-<p><strong>Verified with Glassfish Server Open Source Edition 
3.1.1</strong></p>
-
-<p>1. Make sure a cxf-rt-transport-http-jetty dependency is excluded during 
the war build</p>
-
-<p>2. If a custom JAX-RS <a shape="rect" class="external-link" 
href="http://jsr311.java.net/nonav/releases/1.1/index.html"; 
rel="nofollow">Application</a> is included then<br clear="none">
-use a <a shape="rect" 
href="http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring";>CXFNonSpringJaxrsServlet</a>
 to reference the Application implementation class and either <br clear="none">
- 2.1 Disable the Jersey scanning the custom web applications. Setting the 
following system property may help:<br clear="none">
- 
"-Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext"</p>
-
-<p> 2.2 Remove jersey-gf-server.jar from $GLASSFISH_HOME/glassfish/modules</p>
-
-<h2 id="JAX-RSDeployment-JBoss">JBoss</h2>
-
-<p><strong>Verified with JBoss AS 7.1.0.CR1b</strong></p>
-
-<p>1. If a custom JAX-RS <a shape="rect" class="external-link" 
href="http://jsr311.java.net/nonav/releases/1.1/index.html"; 
rel="nofollow">Application</a> is included then<br clear="none">
-use a <a shape="rect" 
href="http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring";>CXFNonSpringJaxrsServlet</a>
 to reference the Application implementation class and either </p>
-
-<p> 1.1 Disable the RestEasy scanning the custom web applications (TODO: 
specify how this actually can be done)<br clear="none">
- 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.</p>
-
-<p>2. JBoss does not support URI path slashes by default: <a shape="rect" 
class="external-link" href="http://securitytracker.com/id/1018110"; 
rel="nofollow">http://securitytracker.com/id/1018110</a></p>
-
-<h2 id="JAX-RSDeployment-WebLogic">WebLogic</h2>
-
-<p><strong>Verified with WebLogic Server 12c (12.1.1)</strong></p>
-
-<h3 id="JAX-RSDeployment-SpecifyingaWebLogicspecificJSPservlet">Specifying a 
WebLogic specific JSP servlet</h3>
-
-<p>If you configure CXFServlet to redirect to custom JSP pages then you need 
to add the following declaration to web.xml:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[
-&lt;servlet&gt;
+</div><p>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.</p><h1 id="JAX-RSDeployment-ServletContainers">Servlet 
Containers</h1><h2 id="JAX-RSDeployment-Tomcat">Tomcat</h2><p>1. System 
"org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH"<br clear="none"> 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.<br clear="none"> 2. When using mod_jk - ensure that the JkOptions 
setting has +ForwardURICompatUnparsed set. <br clear="none"> 3. Windows: 
upgrade isapi_redirect.dll if you see URI containing encoded spaces being 
decoded by Tomcat.</p><h1 id="JAX-RSDeployment-ApplicationServers">Application 
Servers</h1><h2 
id="JAX-RSDeployment-Glassfish">Glassfish</h2><p><strong>Verified with 
Glassfish Server Open Source Edition 3.1.1</strong></p><p>1. Make sure a 
 cxf-rt-transport-http-jetty dependency is excluded during the war 
build</p><p>2. If a custom JAX-RS <a shape="rect" class="external-link" 
href="http://jsr311.java.net/nonav/releases/1.1/index.html"; 
rel="nofollow">Application</a> is included then<br clear="none"> use a <a 
shape="rect" 
href="http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring";>CXFNonSpringJaxrsServlet</a>
 to reference the Application implementation class and either <br clear="none"> 
2.1 Disable the Jersey scanning the custom web applications. Setting the 
following system property may help:<br clear="none"> 
"-Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext"</p><p>2.2
 Remove jersey-gf-server.jar from $GLASSFISH_HOME/glassfish/modules</p><h2 
id="JAX-RSDeployment-JBoss">JBoss</h2><p><strong>Verified with JBoss AS 
7.1.0.CR1b</strong></p><p>1. If a custom JAX-RS <a shape="rect" 
class="external-link
 " href="http://jsr311.java.net/nonav/releases/1.1/index.html"; 
rel="nofollow">Application</a> is included then<br clear="none"> use a <a 
shape="rect" 
href="http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-ConfiguringJAXRSservicesincontainerwithoutSpring";>CXFNonSpringJaxrsServlet</a>
 to reference the Application implementation class and either</p><p>1.1 Disable 
the RestEasy scanning the custom web applications (TODO: specify how this 
actually can be done)<br clear="none"> 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.</p><p>2. JBoss does not support URI path slashes by default: <a 
shape="rect" class="external-link" href="http://securitytracker.com/id/1018110"; 
rel="nofollow">http://securitytracker.com/id/1018110</a></p><h2 
id="JAX-RSDeployment-WebLogic">WebLogic</h2><p><strong>Verified with WebLogic 
Server 12c (12.1.1)</strong></p><h3 i
 d="JAX-RSDeployment-SpecifyingaWebLogicspecificJSPservlet">Specifying a 
WebLogic specific JSP servlet</h3><p>If you configure CXFServlet to redirect to 
custom JSP pages then you need to add the following declaration to 
web.xml:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[&lt;servlet&gt;
  &lt;servlet-name&gt;jsp&lt;/servlet-name&gt;
  &lt;servlet-class&gt;weblogic.servlet.JSPServlet&lt;/servlet-class&gt;
 &lt;/servlet&gt; 
 ]]></script>
-</div></div>
-
-<h3 id="JAX-RSDeployment-CXFRuntimeDelegate">CXF RuntimeDelegate</h3>
-
-<p>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 </p>
-
-<h3 id="JAX-RSDeployment-SelectingWoodstoxasthedefaultparser">Selecting 
Woodstox as the default parser</h3>
-
-<p>WebLogic requires the following update to the proprietary deployment 
descriptor weblogic.xml:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[
-  &lt;container-descriptor&gt;
+</div></div><h3 id="JAX-RSDeployment-CXFRuntimeDelegate">CXF 
RuntimeDelegate</h3><p>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</p><h3 
id="JAX-RSDeployment-SelectingWoodstoxasthedefaultparser">Selecting Woodstox as 
the default parser</h3><p>WebLogic requires the following update to the 
proprietary deployment descriptor weblogic.xml:</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[  &lt;container-descriptor&gt;
    &lt;!-- SNIP --&gt;
    &lt;prefer-web-inf-classes&gt;true&lt;/prefer-web-inf-classes&gt;
   &lt;/container-descriptor&gt;
 ]]></script>
-</div></div>
-
-<p>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.<br clear="none">
-Please see this <a shape="rect" class="external-link" 
href="https://forums.oracle.com/forums/message.jspa?messageID=9953045"; 
rel="nofollow">thread</a> for more information.</p>
-
-<h2 id="JAX-RSDeployment-Geronimo">Geronimo</h2>
-
-<h3 id="JAX-RSDeployment-CXFRuntimeDelegate.1">CXF RuntimeDelegate</h3>
-
-<p>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.</p></div>
+</div></div><p>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.<br clear="none"> Please see this <a 
shape="rect" class="external-link" 
href="https://forums.oracle.com/forums/message.jspa?messageID=9953045"; 
rel="nofollow">thread</a> for more information.</p><h3 
id="JAX-RSDeployment-HowtouseCXFJAX-RS2.0ifWebLogicshipsJAX-RS1.1">How to use 
CXF JAX-RS 2.0 if WebLogic ships JAX-RS 1.1</h3><p>Please see the following 
email <a shape="rect" class="external-link" 
href="http://cxf.547215.n5.nabble.com/jaxrs-cxf-deployment-issues-on-weblogic-12c-tp5742398p5756013.html";
 rel="nofollow">message</a>.</p><h2 
id="JAX-RSDeployment-Geronimo">Geronimo</h2><h3 
id="JAX-RSDeployment-CXFRuntimeDelegate.1">CXF RuntimeDelegate</h3><p>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.</p></div>
            </div>
            <!-- Content -->
          </td>


Reply via email to