Tomcat 8.5迁移至WebSphere应用部署报错求助

Hey there, let's dig into this WebSphere deployment issue you're facing—those CXF-related class conflicts are a common headache when moving apps from Tomcat to WebSphere, but we can work through them.

First, let's break down the error chain to get to the root cause:
The bottom-line issue is java.lang.IncompatibleClassChangeError: org.apache.neethi.AssertionBuilderFactory—this means the version of the Neethi library (a critical CXF dependency) packaged in your WAR is incompatible with the version WebSphere ships with out of the box. The upper exceptions (ExtensionException and BeanInstantiationException) are just symptoms of this core class conflict.

WebSphere comes pre-installed with its own versions of CXF and Neethi in its plugins directory. When you deploy your WAR (which likely includes the CXF/Neethi versions you used in Tomcat), the classloader gets confused between the two sets of libraries. Even switching between parent-first/last classloader modes might not be enough if you don't explicitly manage which libraries are loaded where.

Here's what you can try to fix this:

1. Audit Your Dependencies First #

Start by confirming exactly what versions of CXF and Neethi your WAR contains. If you're using Maven, run this command in your project root:

mvn dependency:tree

Look for entries like org.apache.neethi:neethi and org.apache.cxf to note their versions. Then compare these to WebSphere's built-in versions—you can find WebSphere's copies in [WAS_INSTALL_ROOT]/plugins (look for JARs named com.ibm.ws.cxf.* and org.apache.neethi.*).

2. Adjust Maven Dependencies to Avoid Conflict #

If WebSphere's CXF/Neethi version is compatible with your app, exclude the conflicting libraries from your WAR so WebSphere uses its own. Add these exclusions to your CXF dependencies in pom.xml:

<dependency>
    <groupId>org.apache.cxf</groupId>
    <artifactId>cxf-spring-boot-starter-jaxws</artifactId> <!-- Replace with your specific CXF artifact -->
    <version>your-cxf-version</version>
    <exclusions>
        <exclusion>
            <groupId>org.apache.neethi</groupId>
            <artifactId>neethi</artifactId>
        </exclusion>
        <exclusion>
            <groupId>org.apache.cxf</groupId>
            <artifactId>cxf-core</artifactId>
        </exclusion>
        <exclusion>
            <groupId>org.apache.cxf</groupId>
            <artifactId>cxf-rt-ws-policy</artifactId>
        </exclusion>
        <!-- Add other CXF modules that WebSphere provides out of the box -->
    </exclusions>
</dependency>

Rebuild your WAR and redeploy to WebSphere.

3. Fine-Tune WebSphere Classloader Settings #

If WebSphere's built-in library versions are too old for your app, you need to force your WAR's libraries to load first. You already tried parent-first/last, but let's add more specificity:

1. In the WebSphere Admin Console, go to Applications > Application Types > WebSphere enterprise applications > [Your App]
2. Navigate to Class loading and update detection
   • Set Class loader policy to Application
   • Set Class loading order to Classes loaded with local class loader first (parent last)
   • Add Filtered classes to block WebSphere from loading its own conflicting versions:
     • Add entries like:
       • org.apache.neethi.*
       • org.apache.cxf.ws.policy.*
       • org.apache.cxf.bus.extension.*
         This tells WebSphere to ignore its own copies of these classes and use the ones from your WAR.

4. Use WebSphere Shared Libraries (For Multi-App Scenarios) #

If you have multiple apps needing the same compatible CXF/Neethi versions, create a shared library:

1. Go to Environment > Shared libraries in the admin console
2. Create a new library pointing to your compatible CXF/Neethi JARs
3. Return to your app's configuration, under Shared library references, add this library
4. Ensure the shared library's classloader order is set to Use application class loader first

5. Verify Class Loading with Tracing #

If you're still stuck, enable classloader tracing to see exactly where classes are being loaded from:

1. Go to Troubleshooting > Logs and trace > [Your Server] > Debugging service
2. Under Class loading, check Enable class loading trace
3. Redeploy your app and check the logs—look for lines like Loaded class org.apache.neethi.AssertionBuilderFactory from... to confirm the correct JAR is being used.

These steps should resolve the incompatible class change error and the subsequent CXF bean instantiation issues.

内容的提问来源于stack exchange，提问作者Sairam Sattar