You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cxf.apache.org by bu...@apache.org on 2013/02/25 18:48:02 UTC
svn commit: r851898 - in /websites/production/cxf/content:
cache/docs.pageCache
docs/application-server-specific-configuration-guide.html
Author: buildbot
Date: Mon Feb 25 17:48:02 2013
New Revision: 851898
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/application-server-specific-configuration-guide.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/application-server-specific-configuration-guide.html
==============================================================================
--- websites/production/cxf/content/docs/application-server-specific-configuration-guide.html (original)
+++ websites/production/cxf/content/docs/application-server-specific-configuration-guide.html Mon Feb 25 17:48:02 2013
@@ -123,39 +123,47 @@ Apache CXF -- Application Server Specifi
<div class="wiki-content">
<div id="ConfluenceContent"><p>This document provides app server-specific configuration information for running Apache CXF.</p>
<style type="text/css">/*<![CDATA[*/
-div.rbtoc1331221576886 {margin-left: 1.5em;padding: 0px;}
-div.rbtoc1331221576886 ul {list-style: disc;margin-left: 0px;padding-left: 20px;}
-div.rbtoc1331221576886 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1361811507075 {margin-left: 1.5em;padding: 0px;}
+div.rbtoc1361811507075 ul {list-style: disc;margin-left: 0px;padding-left: 20px;}
+div.rbtoc1361811507075 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="rbtoc1331221576886">
-<ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-JBoss">JBoss</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-WebLogic">WebLogic</a></li><ul><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Putjarsinendorsedfolder">Put jars in endorsed folder</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Packwarinanear%2Cdeploytheearwithweblogicapplication.xml">Pack war in an ear, deploy the ear with weblogic-application.xml</a></li></ul></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Websphere">Websphere</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-ForWebSphereVersions%3C6.1.0.29">For WebSphere Versions < 6.1.0.29</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-NoWebServicesFeaturePackforWebSphereinstalled">No Web Services Feature Pack for WebSphere installed</a></li><ul><li
><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-putjarintheendorsedfolder">put jar in the endorsed folder</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Addyourownclassloader">Add your own class loader</a></li></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-WebServicesFeaturePackforWebSphereInstalled">Web Services Feature Pack for WebSphere Installed</a></li></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-ForWebSphere6.1.0.29%2CV7andV8">For WebSphere 6.1.0.29+, V7 and V8</a></li></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Glassfish">Glassfish</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-OC4J">OC4J</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Disclaimer">Disclaimer</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Background">Background</a
></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Configurationoverview">Configuration overview</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-OracleOC4Jclassloading">Oracle OC4J class loading</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Neededcomponents">Needed components</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Preparingstaxapi">Preparing stax-api</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-ReplacetheOracleXMLparserwithXerces">Replace the Oracle XML parser with Xerces</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-GetridofOC4JJAXWSlibraries">Get rid of OC4J JAX-WS libraries</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-swappingOracle%7B%7Bwsdl.jar%7D%7Dwith%7B%7Bwsdl4j.jar%7D%7Dand%7B%7Bjaxb.jar%7D%7DAPIwith%7B%7Bjaxbapi2.0.jar%7D%7D">swappin
g Oracle <tt>wsdl.jar</tt> with <tt>wsdl4j.jar</tt> and <tt>jaxb.jar</tt> API with <tt>jaxb-api-2.0.jar</tt></a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Deployingapplications">Deploying applications</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-OracleFAQ">Oracle FAQ</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-I%27mgetting%7B%7Bjava.lang.ClassCastException%3Aorg.apache.xerces.jaxp.DocumentBuilderFactoryImpl%7D%7D">I'm getting <tt>java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</tt></a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-IcannotgetWSDL%28gettingHTTP500accesingmyCXFserviceWSDLwith">I cannot get WSDL (getting HTTP 500 accesing my CXF service WSDL with http://myshot/myservice?wsdl)</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-I%27mgetting%7B%7Bjava.lang.NoSuchMethodExcep
tion%3Aoracle.j2ee.ws.wsdl.extensions.soap.SOAPBodyImpl.getElementType%28%29%7D%7D">I'm getting <tt>java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBodyImpl.getElementType()</tt></a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Icannotgetittoworkstill">I cannot get it to work still</a></li></ul></ul></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-IntegrationwithApplicationServerFAQ">Integration with Application Server FAQ</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Resources">Resources</a></li></ul></div>
+/*]]>*/</style><div class="rbtoc1361811507075">
+<ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-JBossApplicationServer">JBoss Application Server</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-WebLogic">WebLogic</a></li><ul><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Putjarsinendorsedfolder">Put jars in endorsed folder</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Packwarinanear%2Cdeploytheearwithweblogicapplication.xml">Pack war in an ear, deploy the ear with weblogic-application.xml</a></li></ul></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Websphere">Websphere</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-ForWebSphereVersions%3C6.1.0.29">For WebSphere Versions < 6.1.0.29</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-NoWebServicesFeaturePackforWebSphereinstalled">No Web Services Feature Pack for
WebSphere installed</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-putjarintheendorsedfolder">put jar in the endorsed folder</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Addyourownclassloader">Add your own class loader</a></li></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-WebServicesFeaturePackforWebSphereInstalled">Web Services Feature Pack for WebSphere Installed</a></li></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-ForWebSphere6.1.0.29%2CV7andV8">For WebSphere 6.1.0.29+, V7 and V8</a></li></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Glassfish">Glassfish</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-OC4J">OC4J</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Disclaimer">Disclaimer</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigur
ationGuide-Background">Background</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Configurationoverview">Configuration overview</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-OracleOC4Jclassloading">Oracle OC4J class loading</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Neededcomponents">Needed components</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Preparingstaxapi">Preparing stax-api</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-ReplacetheOracleXMLparserwithXerces">Replace the Oracle XML parser with Xerces</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-GetridofOC4JJAXWSlibraries">Get rid of OC4J JAX-WS libraries</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-swappingOracle%7B%7Bwsdl.jar%7D%7Dwith%7B%7Bwsdl4j.jar%7D%7Dand%7B%7Bjaxb.jar%7D%7DAPIwit
h%7B%7Bjaxbapi2.0.jar%7D%7D">swapping Oracle <tt>wsdl.jar</tt> with <tt>wsdl4j.jar</tt> and <tt>jaxb.jar</tt> API with <tt>jaxb-api-2.0.jar</tt></a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Deployingapplications">Deploying applications</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-OracleFAQ">Oracle FAQ</a></li><ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-I%27mgetting%7B%7Bjava.lang.ClassCastException%3Aorg.apache.xerces.jaxp.DocumentBuilderFactoryImpl%7D%7D">I'm getting <tt>java.lang.ClassCastException: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</tt></a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-IcannotgetWSDL%28gettingHTTP500accesingmyCXFserviceWSDLwith">I cannot get WSDL (getting HTTP 500 accesing my CXF service WSDL with http://myshot/myservice?wsdl)</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-I%27mgett
ing%7B%7Bjava.lang.NoSuchMethodException%3Aoracle.j2ee.ws.wsdl.extensions.soap.SOAPBodyImpl.getElementType%28%29%7D%7D">I'm getting <tt>java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBodyImpl.getElementType()</tt></a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Icannotgetittoworkstill">I cannot get it to work still</a></li></ul></ul></ul><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-IntegrationwithApplicationServerFAQ">Integration with Application Server FAQ</a></li><li><a shape="rect" href="#ApplicationServerSpecificConfigurationGuide-Resources">Resources</a></li></ul></div>
-<h2><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-JBoss"></a>JBoss</h2>
+<h2><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-JBossApplicationServer"></a>JBoss Application Server</h2>
-<p>If you package the war in the ear, you might need to add the jboss specific file (jboss-app.xml) in the $EAR/META-INF folder to config the classloader.</p>
+<p>JBoss Application Server (JBoss AS) comes with its own webservices stack (JBossWS) in order for providing full JavaEE support.<br clear="none">
+Starting from JBoss AS 6 M4, the default webservices stack is internally based on Apache CXF; as a consequence users might experiment classloading issues with classes from both the CXF libraries and its dependencies if included in deployments and not properly isolated. Please refer to the relevant JBoss AS documentation for details on how to turn on classloading isolation on the application server version in use.</p>
+
+<p>In particular, when willing to run Apache CXF based applications on top of JBoss AS 7 series, users have basically two options:</p>
+<ul><li>use JBoss AS as if it was a servlet container with no WS functionalities: this basically implies disabling the webservices subsystem for the user deployment, hence preventing the AS webservices stack from processing the ws endpoint deployment and letting the CXF libs included in the archive deal with any WS invocations when CXFServlet is hit; the webservices subsystem is turned off by adding a jboss-deployment-descriptor.xml as follows to the ws endpoint deployment:
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
-<span class="code-tag"><?xml version=<span class="code-quote">"1.0"</span> encoding=<span class="code-quote">"UTF-8"</span>?></span>
-<span class="code-tag"><jboss-app></span>
- <span class="code-tag"><loader-repository></span>
- apache.cxf:loader=spring_http.ear
- <span class="code-tag"><loader-repository-config></span>
- java2ParentDelegation=false
- <span class="code-tag"></loader-repository-config></span>
- <span class="code-tag"></loader-repository></span>
-<span class="code-tag"></jboss-app></span>
+<span class="code-tag"><jboss-deployment-structure xmlns=<span class="code-quote">"urn:jboss:deployment-structure:1.2"</span>></span>
+ <span class="code-tag"><deployment></span>
+ <span class="code-tag"><exclude-subsystems></span>
+ <span class="code-tag"><subsystem name=<span class="code-quote">"webservices"</span> /></span>
+ <span class="code-tag"></exclude-subsystems></span>
+ <span class="code-tag"></deployment></span>
+<span class="code-tag"></jboss-deployment-structure></span>
</pre>
</div></div>
-<p>If you are coming across LinkageErrors involving the QName class, try repackaging the stax-api jar without the javax.xml.namespace.QName class.  (In JBoss 4.0.5GA at least) a conflicting version of this class is included in JBoss's lib and lib/endorsed directories.  This was the only way I could get CXF working in my environment.</p>
+<p>this approach offers the fastest route to deploying CXF apps on JBoss AS; the drawback is that no special ws integration with JBoss AS internals is available</p></li></ul>
+
+
+<ul><li>rely on JBossWS integration and the Apache CXF libraries included in the application server (<a shape="rect" class="external-link" href="https://docs.jboss.org/author/display/AS71/Webservices+reference+guide" rel="nofollow">documentation</a>): this implies removing any Apache CXF libs from the ws deployment as well as any other dependencies which is already included in JBoss AS (including any Java EE API jar); if included, the optional web.xml descriptor is to be rewritten according to JBossWS convention (see <a shape="rect" class="external-link" href="https://docs.jboss.org/author/display/AS71/JAX-WS+User+Guide" rel="nofollow">documentation</a>); the Spring support is optional in JBoss AS and Spring based endpoint declaration is not the default/preferred configuration approach for ws endpoints, hence users willing to declare endpoints using Spring needs to create a org.springframework.spring module and put their endpoint declarations in a jbossws-cxf.xml descriptor;
if the user application makes use of any lib besides tha JavaEE api, proper module <a shape="rect" class="external-link" href="https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7" rel="nofollow">dependencies</a> are to be declared either using the jboss-deployment-structure.xml descriptor or the archive MANIFEST.MF (few directions on ws modules available <a shape="rect" class="external-link" href="https://docs.jboss.org/author/display/AS71/JBoss+Modules+and+WS+applications" rel="nofollow">here</a>)</li></ul>
+
+
+<p>The second approach allows leveraging the full JavaEE 6 stack (including e.g. JSR-109) as well as specific ws integration with JBoss AS internals.</p>
<h2><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-WebLogic"></a>WebLogic</h2>
<p>There are two ways to deploy a CXF WAR archive in WebLogic. (<b>Note: This has been validated on WebLogic9.2.</b>)</p>
-<h4><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-Putjarsinendorsedfolder"></a>Put jars in endorsed folder </h4>
+<h4><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-Putjarsinendorsedfolder"></a>Put jars in endorsed folder</h4>
<ul><li>Put the geronimo-ws-metadata_2.0_spec-1.1.1.jar in the $Weblogic_Home/jdk_../jre/lib/endorsed folder.</li><li>Deploy the CXF war in weblogic.<br clear="none">
- (This way is not recommended, since it might break the application server itself. The method below is preferred, as it impacts a single module only.)</li></ul>
+(This way is not recommended, since it might break the application server itself. The method below is preferred, as it impacts a single module only.)</li></ul>
<h4><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-Packwarinanear%2Cdeploytheearwithweblogicapplication.xml"></a>Pack war in an ear, deploy the ear with weblogic-application.xml</h4>
@@ -199,7 +207,7 @@ div.rbtoc1331221576886 li {margin-left:
<p>The prefer-application-packages element you see above sets up WebLogic's <a shape="rect" class="external-link" href="http://e-docs.bea.com/wls/docs100/programming/classloading.html#wp1097187" rel="nofollow">Filtering Classloader</a>. Each class whose package matches one of the package-name elements listed will be searched for first within the EAR before relying on the WebLogic system classloader's version. If a package for a particular class is not listed here, WebLogic will try to load its own (possibly older) version first, so if you are getting deployment errors due to any particular class you might wish to add its package here.</p>
-<p>Also note you can, and may need to, specify other options in the weblogic-application.xml file such as XML processing factories as shown <a shape="rect" class="external-link" href="http://cxf.547215.n5.nabble.com/Getting-error-while-deploying-on-weblogic-9-2-but-able-to-do-in-tomcat-td554060.html#a554061" rel="nofollow">here</a>. See the WebLogic <a shape="rect" class="external-link" href="http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/app_xml.html#wp1064995" rel="nofollow">guide</a> for more information. </p>
+<p>Also note you can, and may need to, specify other options in the weblogic-application.xml file such as XML processing factories as shown <a shape="rect" class="external-link" href="http://cxf.547215.n5.nabble.com/Getting-error-while-deploying-on-weblogic-9-2-but-able-to-do-in-tomcat-td554060.html#a554061" rel="nofollow">here</a>. See the WebLogic <a shape="rect" class="external-link" href="http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/app_xml.html#wp1064995" rel="nofollow">guide</a> for more information.</p>
<ul><li>Run "jar cvf ..." command to create the ear and then deploy it. Alternatively, this <a shape="rect" class="external-link" href="http://www.jroller.com/gmazza/entry/deploying_webservices_on_weblogic" rel="nofollow">blog entry</a> provides a Mavenized method of building the EAR.</li></ul>
@@ -208,9 +216,11 @@ div.rbtoc1331221576886 li {margin-left:
<h3><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-ForWebSphereVersions%3C6.1.0.29"></a>For WebSphere Versions < 6.1.0.29</h3>
-<p>Adding jars to the 'endorsed' folder appears to be the main solution: </p>
+<p>Adding jars to the 'endorsed' folder appears to be the main solution:</p>
<h4><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-NoWebServicesFeaturePackforWebSphereinstalled"></a>No Web Services Feature Pack for WebSphere installed</h4>
+
+
<h5><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-putjarintheendorsedfolder"></a>put jar in the endorsed folder</h5>
<ul><li>put the wsdl4j-1.6.1.jar in the $WebSphere_HOME/java/jre/lib/endorsed folder.</li><li>In the WebSphere console, find the specific enterprise application, click the "Class loading and update detection".
@@ -226,47 +236,48 @@ div.rbtoc1331221576886 li {margin-left:
<p>If you put your wsdl4j-1.6.1 jar in $WAS_HOME/java/jre/lib/endorsed, all your applications will depend on your version of wsdl4j. Another solution is to create a new class loader in your server which loads before parent class loader, create a shared library with your version of wsdl4j, and add this shared library to your new class loader. This version of wsdl4j will only be available for your specific server and not affect applications running in other servers.</p>
<p><b>Step by step</b></p>
-<ol><li>In the WAS console navigate to <b>Environment > Shared Libraries</b></li><li>Select the scope you wish your library should be visible in</li><li>Click <b>New</b> and set values ex: <tt>name=MYAPP_SHARED_LIB, classpath=PATH_TO/wsdl4j-1.6.2.jar</tt> and <b>Save</b></li><li>Navigate to <b>Application servers > [your server name]</b> <b>> Java and Process Management > Class loader > New</b></li><li>Select <b>Classes loaded with application class loader first</b> and <b>Save</b></li><li>Select your new class loader and click <b>Shared library references</b></li><li>Add your shared library (MYAPP_SHARED_LIB) <b>Save</b> and restart your server.<br clear="none" class="atl-forced-newline"></li></ol>
+<ol><li>In the WAS console navigate to <b>Environment > Shared Libraries</b></li><li>Select the scope you wish your library should be visible in</li><li>Click <b>New</b> and set values ex: <tt>name=MYAPP_SHARED_LIB, classpath=PATH_TO/wsdl4j-1.6.2.jar</tt> and <b>Save</b></li><li>Navigate to <b>Application servers > [your server name]</b> <b>> Java and Process Management > Class loader > New</b></li><li>Select <b>Classes loaded with application class loader first</b> and <b>Save</b></li><li>Select your new class loader and click <b>Shared library references</b></li><li>Add your shared library (MYAPP_SHARED_LIB) <b>Save</b> and restart your server.
+<br clear="none" class="atl-forced-newline"></li></ol>
<p>Tested in WAS 6.1 only but should work in earlier versions as well.</p>
<p>Another user running WS6.1 FP 23 without the web services feature pack came up with this solution that seemed to work for them:</p>
<blockquote>
-<p>Create a shared library with the following jars: <br clear="none">
-jsr173_api-1.0.jar <br clear="none">
-jaxp-ri-1.4.2.jar <br clear="none">
-saaj-impl-1.3.2.jar <br clear="none">
-wsdl4j-1.6.2.jar </p>
+<p>Create a shared library with the following jars:<br clear="none">
+jsr173_api-1.0.jar<br clear="none">
+jaxp-ri-1.4.2.jar<br clear="none">
+saaj-impl-1.3.2.jar<br clear="none">
+wsdl4j-1.6.2.jar</p>
<p>Create a new parent-first classloader and have it reference the shared library you just created. Restart everything and it should work.</p></blockquote>
<h4><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-WebServicesFeaturePackforWebSphereInstalled"></a>Web Services Feature Pack for WebSphere Installed</h4>
+
<p>Things are way more complicated if the Web Services Feature Pack for WebSphere is installed. With this feature pack installed, it is impossible to deploy an application using CXF, because the WebSphere Web Services engine starts parsing the JAX-WS annotations of the services and tries to deploy the services.</p>
<p>Up to fixpack 27 (6.1.0.27) there was no possibility to disable the WebSphere Web Services engine.</p>
<h3><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-ForWebSphere6.1.0.29%2CV7andV8"></a>For WebSphere 6.1.0.29+, V7 and V8</h3>
-<p>Follow the PDF download given within this IBM developerWorks article:
-<a shape="rect" class="external-link" href="http://www.ibm.com/developerworks/websphere/library/techarticles/1001_thaker/1001_thaker.html" rel="nofollow">http://www.ibm.com/developerworks/websphere/library/techarticles/1001_thaker/1001_thaker.html</a></p>
+<p>Follow the PDF download given within this IBM developerWorks article:<a shape="rect" class="external-link" href="http://www.ibm.com/developerworks/websphere/library/techarticles/1001_thaker/1001_thaker.html" rel="nofollow">http://www.ibm.com/developerworks/websphere/library/techarticles/1001_thaker/1001_thaker.html</a></p>
<p>As described in the PDF, you'll need to change the Classloader order to "Classes loaded with local class loader first (parent last)" and to disable the IBM web services engine, either for the JVM as a whole or for the particular module.</p>
<p>To disable for the whole JVM, set the JVM property</p>
-<p> com.ibm.websphere.webservices.DisableIBMJAXWSEngine=true</p>
+<p>com.ibm.websphere.webservices.DisableIBMJAXWSEngine=true</p>
<p>or to disable the engine just for a specific module by adding</p>
-<p> DisableIBMJAXWSEngine: true</p>
+<p>DisableIBMJAXWSEngine: true</p>
<p>to WAR/META-INF/MANIFEST.MF.</p>
-<p>Another issue that comes up with certain versions of WebSphere is an incompatibility with the SAAJ implementation. It is recommended to use the org.apache.servicemix.bundles.saaj-impl-1.3.18_1.jar saaj impl available from <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saaj-impl/1.3.18_1/" rel="nofollow">http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saaj-impl/1.3.18_1/</a> as that contains a recent version of SAAJ along with it's required DOM implementation which will work on the IBM JDK. </p>
+<p>Another issue that comes up with certain versions of WebSphere is an incompatibility with the SAAJ implementation. It is recommended to use the org.apache.servicemix.bundles.saaj-impl-1.3.18_1.jar saaj impl available from <a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saaj-impl/1.3.18_1/" rel="nofollow">http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saaj-impl/1.3.18_1/</a> as that contains a recent version of SAAJ along with it's required DOM implementation which will work on the IBM JDK.</p>
-<p>One user has reported that he was able to get CXF working on WebSphere with a minimal set of CXF jars by following the above <br clear="none">
+<p>One user has reported that he was able to get CXF working on WebSphere with a minimal set of CXF jars by following the above<br clear="none">
procedures and using the list of jars:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
@@ -305,12 +316,12 @@ xmlschema-core-2.0.1.jar
<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
-<span class="code-tag"><?xml version=<span class="code-quote">"1.0"</span> encoding=<span class="code-quote">"UTF-8"</span>?></span>
-<!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD
-Application Server 9.0 Servlet 2.5//EN'
-'http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd'>
-<span class="code-tag"><sun-web-app></span>
-<span class="code-tag"><class-loader delegate=<span class="code-quote">"false"</span>/></span>
+<span class="code-tag"><?xml version=<span class="code-quote">"1.0"</span> encoding=<span class="code-quote">"UTF-8"</span>?></span>
+<!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD
+Application Server 9.0 Servlet 2.5//EN'
+'http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd'>
+<span class="code-tag"><sun-web-app></span>
+<span class="code-tag"><class-loader delegate=<span class="code-quote">"false"</span>/></span>
<span class="code-tag"></sun-web-app></span>
</pre>
</div></div>
@@ -427,7 +438,7 @@ OC4J 10.1.3 comes with <a shape="rect" c
<h5><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-Icannotgetittoworkstill"></a>I cannot get it to work still</h5>
-<p>Try something simple. Download OC4J standalone and bootstrap it from command line directly: <tt>java [options] -jar oc4j.jar</tt>. Enable <a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/api/javax/xml/parsers/SAXParserFactory.html#newInstance()" rel="nofollow">SAX debugging</a>. Be sure You don't include douplicated jars in Your application like <tt>xercesImpl, xalan, xml-apis and geronimo-ws-metadata_2.0_spec-1.1.1.jar</tt>. Review steps above once more. It works <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/wink.gif" height="20" width="20" alt="" border="0">.</p>
+<p>Try something simple. Download OC4J standalone and bootstrap it from command line directly: <tt>java [options] -jar oc4j.jar</tt>. Enable <a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/api/javax/xml/parsers/SAXParserFactory.html#newInstance()" rel="nofollow">SAX debugging</a>. Be sure You don't include douplicated jars in Your application like <tt>xercesImpl, xalan, xml-apis and geronimo-ws-metadata_2.0_spec-1.1.1.jar</tt>. Review steps above once more. It works <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/wink.gif" height="20" width="20" alt="" border="0"> .</p>
<h2><a shape="rect" name="ApplicationServerSpecificConfigurationGuide-IntegrationwithApplicationServerFAQ"></a>Integration with Application Server FAQ</h2>