在WebLogic中部署Spring应用时，如何禁用Java EE（仅保留Servlet容器）

Absolutely! You can absolutely lock down WebLogic to act only as a plain Servlet container, letting Spring and your bundled libraries take full control—no more annoying Java EE interference or version-dependent conflicts. Here’s how to do it step by step:

1. Use weblogic.xml to Override Classloading & Disable EE Services #

Create or update your WEB-INF/weblogic.xml file with these settings to prioritize your app’s libraries and turn off unwanted Java EE components:

<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.7/weblogic-web-app.xsd">

    <!-- Force WebLogic to use your app's libraries instead of its own -->
    <container-descriptor>
        <prefer-application-packages>
            <!-- Spring core and related packages -->
            <package-name>org.springframework.*</package-name>
            <!-- Add all bundled libs that might clash with WebLogic (Jackson, Validator, etc.) -->
            <package-name>com.fasterxml.jackson.*</package-name>
            <package-name>javax.validation.*</package-name>
            <!-- Disable WebLogic's JPA implementation -->
            <package-name>javax.persistence.*</package-name>
            <!-- Disable WebLogic's JAX-RS if using Spring Boot's -->
            <package-name>javax.ws.rs.*</package-name>
        </prefer-application-packages>
        
        <!-- Ignore Java EE annotations like @EJB or @Resource so WebLogic doesn't process them -->
        <ignore-annotations>true</ignore-annotations>
    </container-descriptor>

    <!-- Let Spring manage sessions instead of WebLogic -->
    <session-descriptor>
        <cookie-name>JSESSIONID</cookie-name>
        <session-timeout>30</session-timeout>
    </session-descriptor>

    <!-- Disable WebLogic's JSP compiler if Spring handles view rendering -->
    <jsp-descriptor>
        <keepgenerated>false</keepgenerated>
        <page-check-seconds>0</page-check-seconds>
    </jsp-descriptor>

    <context-root>/your-app-name</context-root>
</weblogic-web-app>

• Critical Tip: The prefer-application-packages section is make-or-break—it tells WebLogic to load your app’s versions of these packages before its own. Be sure to add all packages from your bundled libraries that could clash with WebLogic’s Java EE implementations.

2. Spring Boot-Specific Tweaks (If Applicable) #

If you’re deploying a Spring Boot app, adjust your build file to exclude unnecessary Java EE dependencies and align with WebLogic’s servlet environment:

Maven Example: #

<dependencies>
    <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
        <exclusions>
            <!-- Exclude Tomcat since we're using WebLogic as the container -->
            <exclusion>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-starter-tomcat</artifactId>
            </exclusion>
            <!-- Exclude servlet API since WebLogic provides it -->
            <exclusion>
                <groupId>javax.servlet</groupId>
                <artifactId>javax.servlet-api</artifactId>
            </exclusion>
        </exclusions>
    </dependency>
    <!-- Add WebLogic-compatible servlet API as provided -->
    <dependency>
        <groupId>javax.servlet</groupId>
        <artifactId>javax.servlet-api</artifactId>
        <version>3.1.0</version>
        <scope>provided</scope>
    </dependency>
</dependencies>

• Make sure your app is packaged as a WAR, and your SpringBootServletInitializer is correctly configured to bootstrap Spring without relying on WebLogic’s EE hooks.

3. Admin-Level Global Disabling (Optional) #

If you have WebLogic admin access, you can turn off global Java EE features that might leak into your app:

• Open the WebLogic Console → Domain Structure → Deployments → Your App → Configuration → General
• Uncheck boxes for features like Enable EJB Container, Enable JPA Container, Enable JAX-RS
• Restart the app after making changes

4. Verify Your Setup #

To confirm WebLogic isn’t interfering:

• Check server logs for messages confirming your app’s libraries are being loaded instead of WebLogic’s
• Run a quick test to ensure Spring components (like @RestController or @Service) handle requests without EE-specific errors
• Use jar -tvf your-app.war to confirm all required libraries are bundled in WEB-INF/lib

By following these steps, you’ll effectively turn WebLogic into a simple Servlet container, letting Spring and your bundled dependencies run the show—no more unexpected conflicts when updating versions!

内容的提问来源于stack exchange，提问作者Tuomas Toivonen