This document provides app server-specific configuration information for running Apache CXF.
There are two ways to deploy a CXF WAR archive in WebLogic. (Note: This has been validated on WebLogic9.2.)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>spring_http</display-name>
<module>
<web>
<web-uri>spring_http.war</web-uri>
<context-root>spring</context-root>
</web>
</module>
</application>
|
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90">
<application-param>
<param-name>webapp.encoding.default</param-name>
<param-value>UTF-8</param-value>
</application-param>
<prefer-application-packages>
<package-name>javax.jws.*</package-name>
</prefer-application-packages>
</weblogic-application>
|
|
This is the recommend way to deploy since it impacts only a single module. |
Currently, I've only found the endorsed way to make cxf work with websphere. (Note: this has been validated against Websphere6.1.0.0)
And then restart the Websphere server. (Because we changed the endorsed folder, we need to restart it to make it effect).
|
Please make sure your classpath doesn't have the servlet-2.5 library, since WebSphere6.1 is servlet-2.4 compliant! |
Deploy XFire in WebLogic
Understanding WebLogic ClassLoader