


When Tomcat loads Spring-Web modules, does the SPI mechanism really destroy the visibility principle of Java class loaders?
Apr 19, 2025 pm 02:18 PMTomcat and Spring-Web module loading: Analysis of class loading behavior under SPI mechanism
When Tomcat loads Spring-Web module, it uses the Java SPI (Service Provider Interface) mechanism to find and use ServletContainerInitializer
interface implementation class. This involves the load
method of ServiceLoader
and the visibility principle of class loader. Some people question this approach violates the visibility principle of class loaders, so let's analyze it in depth.
The article points out that the ServiceLoader.load
method is ultimately loaded by sun.misc.Launcher.AppClassLoader
to load the implementation class of ServletContainerInitializer
interface. In the code, ServiceLoader.load(service, cl)
uses Thread.currentThread().getContextClassLoader()
to get the class loader. In application servers such as Tomcat, this class loader is usually AppClassLoader
.
Some people think that ServiceLoader.load(service, cl)
is equivalent to ServiceLoader.load(service, null)
. Although the results are similar in some cases, the principles are different. The former explicitly specifies the class loader, while the latter uses the caller's class loader.
Why do anyone think this breaks the visibility principle of class loaders? The key lies in the particularity of the SPI mechanism. The interface in rt.jar
is loaded by BootstrapClassLoader
, but its implementation class is usually in classpath and is loaded by AppClassLoader
. BootstrapClassLoader
cannot be loaded downward, so the thread context class loader needs to load the implementation class. This bypasses the strict hierarchy of the parent delegation model, enabling AppClassLoader
to load classes that BootstrapClassLoader
cannot load. Although the problem was solved, it also deviated from the original intention of the parent delegation model.
It should be emphasized that AppClassLoader
does not directly skip the code of the parent delegation mechanism, and it still follows the parent delegation logic internally. It is only in the SPI scenario that due to the limitations of BootstrapClassLoader
, the final loading work is done by AppClassLoader
, which is a trade-off. The JDBC mechanism is similar. Java only provides interfaces. The specific implementation is provided by the manufacturer, and the restrictions of the parent delegation mechanism are also required to bypass.
Therefore, the SPI mechanism "violates" the strict rules of the parent delegation model to some extent, but this is a necessary compromise and does not completely "destroy" the visibility principle of class loaders. It finds a suitable way to load the implementing class through the thread context class loader.
The above is the detailed content of When Tomcat loads Spring-Web modules, does the SPI mechanism really destroy the visibility principle of Java class loaders?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The core method of building social sharing functions in PHP is to dynamically generate sharing links that meet the requirements of each platform. 1. First get the current page or specified URL and article information; 2. Use urlencode to encode the parameters; 3. Splice and generate sharing links according to the protocols of each platform; 4. Display links on the front end for users to click and share; 5. Dynamically generate OG tags on the page to optimize sharing content display; 6. Be sure to escape user input to prevent XSS attacks. This method does not require complex authentication, has low maintenance costs, and is suitable for most content sharing needs.

To realize text error correction and syntax optimization with AI, you need to follow the following steps: 1. Select a suitable AI model or API, such as Baidu, Tencent API or open source NLP library; 2. Call the API through PHP's curl or Guzzle and process the return results; 3. Display error correction information in the application and allow users to choose whether to adopt it; 4. Use php-l and PHP_CodeSniffer for syntax detection and code optimization; 5. Continuously collect feedback and update the model or rules to improve the effect. When choosing AIAPI, focus on evaluating accuracy, response speed, price and support for PHP. Code optimization should follow PSR specifications, use cache reasonably, avoid circular queries, review code regularly, and use X

User voice input is captured and sent to the PHP backend through the MediaRecorder API of the front-end JavaScript; 2. PHP saves the audio as a temporary file and calls STTAPI (such as Google or Baidu voice recognition) to convert it into text; 3. PHP sends the text to an AI service (such as OpenAIGPT) to obtain intelligent reply; 4. PHP then calls TTSAPI (such as Baidu or Google voice synthesis) to convert the reply to a voice file; 5. PHP streams the voice file back to the front-end to play, completing interaction. The entire process is dominated by PHP to ensure seamless connection between all links.

The top ten authoritative cryptocurrency market and data analysis platforms in 2025 are: 1. CoinMarketCap, providing comprehensive market capitalization rankings and basic market data; 2. CoinGecko, providing multi-dimensional project evaluation with independence and trust scores; 3. TradingView, having the most professional K-line charts and technical analysis tools; 4. Binance market, providing the most direct real-time data as the largest exchange; 5. Ouyi market, highlighting key derivative indicators such as position volume and capital rate; 6. Glassnode, focusing on on-chain data such as active addresses and giant whale trends; 7. Messari, providing institutional-level research reports and strict standardized data; 8. CryptoCompa

This article elaborates on two main methods to realize call hold and unhold in Twilio. The preferred option is to leverage Twilio's Conference feature to easily enable call retention and recovery by updating the conference participant resources, and to customize music retention. Another approach is to deal with independent call legs, which requires more complex TwiML logic, passed, and arrived management, but is more cumbersome than meeting mode. The article provides specific code examples and operation steps to help developers efficiently implement Twilio call control.

The most suitable tools for querying stablecoin markets in 2025 are: 1. Binance, with authoritative data and rich trading pairs, and integrated TradingView charts suitable for technical analysis; 2. Ouyi, with clear interface and strong functional integration, and supports one-stop operation of Web3 accounts and DeFi; 3. CoinMarketCap, with many currencies, and the stablecoin sector can view market value rankings and deans; 4. CoinGecko, with comprehensive data dimensions, provides trust scores and community activity indicators, and has a neutral position; 5. Huobi (HTX), with stable market conditions and friendly operations, suitable for mainstream asset inquiries; 6. Gate.io, with the fastest collection of new coins and niche currencies, and is the first choice for projects to explore potential; 7. Tra

Stablecoins are cryptocurrencies with value anchored by fiat currency or commodities, designed to solve price fluctuations such as Bitcoin. Their importance is reflected in their role as a hedging tool, a medium of trading and a bridge connecting fiat currency with the crypto world. 1. The fiat-collateralized stablecoins are fully supported by fiat currencies such as the US dollar. The advantage is that the mechanism is simple and stable. The disadvantage is that they rely on the trust of centralized institutions. They represent the projects including USDT and USDC; 2. The cryptocurrency-collateralized stablecoins are issued through over-collateralized mainstream crypto assets. The advantages are decentralization and transparency. The disadvantage is that they face liquidation risks. The representative project is DAI. 3. The algorithmic stablecoins rely on the algorithm to adjust supply and demand to maintain price stability. The advantages are that they do not need to be collateral and have high capital efficiency. The disadvantage is that the mechanism is complex and the risk is high. There have been cases of dean-anchor collapse. They are still under investigation.

The real use of battle royale in the dual currency system has not yet happened. Conclusion In August 2023, the MakerDAO ecological lending protocol Spark gave an annualized return of $DAI8%. Then Sun Chi entered in batches, investing a total of 230,000 $stETH, accounting for more than 15% of Spark's deposits, forcing MakerDAO to make an emergency proposal to lower the interest rate to 5%. MakerDAO's original intention was to "subsidize" the usage rate of $DAI, almost becoming Justin Sun's Solo Yield. July 2025, Ethe
