# Spring Framework Spring Framework is a comprehensive programming and configuration framework for modern Java-based enterprise applications, providing features such as dependency injection, web frameworks, data access, and testing support. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Meet Jos Roseboom DevFeed: [Meet Jos Roseboom]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2026-09-11T04:23:25Z Content type: article Language: en Sources: [Vlad Mihalcea]() Topics: [Java](), [Spring Framework](), [Spring Boot](), [Jakarta EE](), [Development]() Tags: [2026](), [article](), [blog](), [community](), [conference](), [framework](), [hibernate](), [interview](), [jakarta-ee](), [java](), [jpa](), [performance](), [performance-tuning](), [spring](), [spring-boot]() ### AI overview An interview with Jos Roseboom about JPA and Hibernate performance tuning, based on his JavaZone talk. He describes production incidents involving exhausted database connections and excessive queries caused by fetching entities and following associations. ### Source excerpt JavaZone 2026 At the beginning of September, I participated in JavaZone for the third time and had the privilege of meeting a lot of passionate software developers willing to share their knowledge with the community. In the first conference day, I attended a very good talk about JPA performance tuning that was delivered by Jos Roseboom and since I enjoyed his talk, I proposed him to gave an interview for this blog. Therefore, in this article we have the pleasure of getting to know Jos and take opportunity of learning about Spring... Read More The post Meet Jos Roseboom appeared first on Vlad Mihalcea. ## The best way to clean up test data with Spring and Hibernate DevFeed: [The best way to clean up test data with Spring and Hibernate]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-11-11T08:05:24Z Content type: tutorial Language: en Sources: [Vlad Mihalcea]() Topics: [Spring Boot](), [Integration testing](), [Testing](), [Java](), [Spring Framework]() Tags: [cleanup](), [hibernate](), [integration-testing](), [java](), [jpa](), [schema](), [spring](), [spring-boot](), [test-data](), [testing](), [truncatemappedobjects]() ### AI overview This tutorial examines how to clean up test data in Spring and Hibernate integration tests. It argues that relying on @DataJpaTest for automatic transaction rollback is not always appropriate and discusses limitations of its SQL logging, including its inability to show bind parameter values or indicate whether batching is used. ### Source excerpt Introduction In this article, I'm going to show you the best way to clean up test data when using Spring and Hibernate. While it's very common to use the @DataJpaTest annotation when implementing integration tests, in this blog post, you will see why you are better off avoiding using this annotation. Why I don't use @DataJpaTest As explained by the manual, Spring Boot provides the @DataJpaTest annotation for Spring Data JPA integration testing. Once the @DataJpaTest annotation is added to an integration test, Spring Boot will make the following changes to the... Read More The post The best way to clean up test data with Spring and Hibernate appeared first on Vlad Mihalcea. ## Twelve years of blogging DevFeed: [Twelve years of blogging]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-09-30T11:35:44Z Content type: opinion Language: en Sources: [Vlad Mihalcea]() Topics: [Development](), [Java](), [Spring Framework](), [Spring Boot](), [Jakarta EE](), [WordPress]() Tags: [anniversary](), [article](), [blog](), [blogging](), [jakarta-ee](), [java](), [software-developer](), [spring](), [spring-boot](), [wordpress](), [writing]() ### AI overview A personal reflection marking twelve years of blogging. The author describes starting the blog while working as a software architect, developing writing experience over time, and finding inspiration in wide-ranging reading. The article also promotes Hypersistence Optimizer for detecting performance issues in JPA and Hibernate data access layers across several Java frameworks. ### Source excerpt Twelve years later! Twelve years ago today, I decided to create this blog on WordPress.com to share whatever I was finding interesting while working as a software architect. Prior to starting this blog, I didn't have any writing experience, which you can clearly see in the first article I've ever published. However, practice makes perfect, and in time, I managed to learn how to express myself in writing, whether it was an article, a social media post, an answer on StackOverflow, or a book. Follow Your Bliss I've always loved to read.... Read More The post Twelve years of blogging appeared first on Vlad Mihalcea. ## The persistent threat: Why major vulnerabilities like Log4Shell and Spring4Shell remain significant DevFeed: [The persistent threat: Why major vulnerabilities like Log4Shell and Spring4Shell remain significant]() Original publisher: [Read original article]() Author: Brian Vermeer Published: 2024-08-29T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [log4j](), [Vulnerabilities](), [Spring Framework](), [Security]() Tags: [application-security](), [awareness](), [blog](), [developer](), [devrel](), [enablement](), [java](), [log4j](), [logging](), [open-source-security](), [security](), [snyk-open-source](), [spring-framework](), [vulnerabilities]() ### AI overview The article examines the continued use of vulnerable Log4j and Spring Framework versions in software projects. It explains how Log4Shell could enable malicious code execution and cites scan data indicating that 21% of companies with production code scanning still had projects vulnerable to Log4Shell. ### Source excerpt Read on to learn about the danger of the continued use of vulnerable Log4j and Spring Framework versions in many projects. ## Spring Dependencies in Gradle Can Be Tricky DevFeed: [Spring Dependencies in Gradle Can Be Tricky]() Original publisher: [Read original article]() Author: piotr-kubowicz Published: 2020-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Backend Development on nexocode]() Topics: [Gradle](), [Dependency management](), [Spring Boot](), [Spring Framework]() Tags: [build-tool](), [dependencies](), [gradle](), [java](), [jvm](), [security](), [spring](), [spring-boot](), [spring-framework]() ### AI overview This article explains why managing Spring dependencies with Gradle can be difficult, especially when applications use multiple Spring projects and related libraries. It recommends importing a Spring-provided BOM instead of managing versions manually, describes the history and limitations of the Spring Dependency Management Plugin, and shows that an attempted Jackson Databind version override may leave the vulnerable version in use. ### Source excerpt Spring is the most popular Java web framework for many years and Gradle has an established position as a build tool. You might expect it's easy to find instructions on how to set up those two together -- yet the Internet is filled with advice that will get you into trouble. The official Spring documentation does not make the situation any better in this case. Using Spring in your applications typically means your classpath contains not only Spring Framework itself, but also other Spring projects like Spring Security plus Spring dependencies that are independent libraries. It may require lots of work to get versions of dependencies right, avoiding incompatible versions being used together. So a much better solution is -- not to manage all those versions manually and choose a set suggested by Spring. Technically speaking: importing a BOM (bill of materials). ## Error handling with @Transactional DevFeed: [Error handling with @Transactional]() Original publisher: [Read original article]() Published: 2019-11-11T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Spring Framework](), [Transactions](), [Exception](), [Error Handling]() Tags: [bug](), [error-handling](), [exception](), [spring](), [spring-framework](), [transactions]() ### AI overview This article explains Spring transaction rollback behavior for runtime and checked exceptions, including how explicit rollback configuration affects checked exceptions. It also discusses how Lombok's @SneakyThrows interacts with @Transactional. ### Source excerpt You probably already know that by default in spring transactions are rolled back only for runtime exceptions. When a checked exception is thrown from your code and you don't explicitly tell spring that it should rollback the transaction then it get's committed. In this post, I'm going to create simple reference material on when transactions are rollback when using Spring and Lombok. Read more ## ProxyFactory and ProxyFactoryBean in Spring DevFeed: [ProxyFactory and ProxyFactoryBean in Spring]() Original publisher: [Read original article]() Published: 2019-06-13T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Spring Framework](), [Java](), [interfaces](), [Framework](), [Code]() Tags: [code](), [framework](), [how-to](), [interfaces](), [java](), [proxy](), [spring]() ### AI overview This tutorial explains how Spring's ProxyFactory and ProxyFactoryBean create object proxies. It compares native Java proxies with CGLIB-based proxies and shows how Spring abstractions can create proxies for interfaces and concrete classes. ### Source excerpt Spring provides many easy to use abstractions and you use many of them without even knowing about them. You probably know that in order to have @Transactional or @Cacheable annotation work spring creates proxies for you (sometimes proxies on top of proxies...), but have you ever wondered how it's happening under the hood? What Creation of object proxies is a cumbersome task. One has to decide if the proxy should be created using native java mechanisms (JdkProxy available only on interfaces) or using cglib and it's complicated interfaces. Read more ## Spring internals - BeanDefinition DevFeed: [Spring internals - BeanDefinition]() Original publisher: [Read original article]() Published: 2019-04-29T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Spring Framework](), [Code](), [implementation]() Tags: [code](), [customization](), [examples](), [extend](), [framework](), [how-to](), [interface](), [interfaces](), [internals](), [spring](), [spring-framework]() ### AI overview A tutorial on Spring Framework BeanDefinition internals explains how bean definitions are discovered, registered, created, and customized. It covers dynamic registration and modification through BeanDefinitionRegistryPostProcessor and BeanDefinitionCustomizer. ### Source excerpt How beans are registered in spring and what is the base of beans creation, how to extend spring's context to our needs? In this post, I'm going to dig into the foundation of many mechanics in spring framework - bean definition. Read more ## spring.factories DevFeed: [spring.factories]() Original publisher: [Read original article]() Published: 2019-03-28T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Spring Boot](), [Spring Framework](), [configuration](), [modules]() Tags: [configuration](), [module](), [spring](), [spring-boot](), [spring-framework]() ### AI overview This developer article explains how Spring Boot uses the spring.factories file and Spring Framework mechanisms to discover module-provided configuration and customize the application context during initialization. It also describes how classpath scanning and conditional configuration support Spring Boot's modular design. ### Source excerpt Have you ever wondered how it's possible that spring-boot is able to pick up whatever you have on the classpath and configure application context to your needs based on some conventions and bit of black magic? In this post, I'm going to dig into spring.factories file on which most of the spring-boot power is based. Read more ## Spring internals - BeanPostProcessor DevFeed: [Spring internals - BeanPostProcessor]() Original publisher: [Read original article]() Published: 2019-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Spring Framework](), [Spring Boot](), [Code](), [implementation](), [IoC (Disambiguation)]() Tags: [boot-process](), [code](), [container](), [context](), [customization](), [execution](), [framework](), [implementation](), [interface](), [spring](), [spring-boot](), [spring-framework]() ### AI overview This article explains Spring's BeanPostProcessor interface and its role during Spring container initialization. It describes how post-processors customize bean instances before and after initialization, can interrupt further processing, and can support examples such as measuring selected method execution times. ### Source excerpt Have you ever wondered how spring does things? How field annotated with @Autowired is populated? How asynchronous or scheduled methods are discovered. In this post, I'm going to take a deeper look and scratch a bit on the surface of spring internals. I'll focus on BeanPostProcessor interface which can be used to achieve interesting things and is used in many various functionalities across spring framework itself. Read more ## Testing MVC in Spring DevFeed: [Testing MVC in Spring]() Original publisher: [Read original article]() Published: 2018-01-30T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Testing](), [Spring MVC](), [Spring Framework](), [REST API](), [Java]() Tags: [controllers](), [how-to](), [java](), [kotlin](), [rest-api](), [spring](), [testing]() ### AI overview A practical guide to testing Spring MVC applications, covering controller tests, separate MVC test groups, minimal test contexts, @WebMvcTest, and strict JSON verification. It also explains how API tests help preserve REST contracts and keep API documentation aligned with the build. ### Source excerpt Most of java web applications is built on top of the Spring Framework. Spring has pretty good support for testing and it is a mistake not to take advantage of features it offers. I've been developing various applications using Spring MVC for some time and I've noticed few patterns for testing that do work. Read more ## Events in spring DevFeed: [Events in spring]() Original publisher: [Read original article]() Published: 2017-08-01T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Spring Framework](), [async](), [generics]() Tags: [async](), [asynchronous](), [framework](), [generics](), [spring](), [transaction-management]() ### AI overview A tutorial on Spring Framework event handling, covering event publication, listener methods, generic event resolution, SpEL filtering, transaction-bound listeners, and asynchronous execution. ### Source excerpt With spring 4.2 (released more than one year ago) serious improvements regarding embedded events were made. You probably already know it, but I've never had a chance to properly investigate it. Lately, when digging into code base of the system I'm currently working on I got an opportunity to see it in action and after quick glimpse, I decided to investigate it a bit further. Read more ## Incidental Inversion of Control DevFeed: [Incidental Inversion of Control]() Original publisher: [Read original article]() Published: 2010-05-28T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [IoC (Disambiguation)](), [Spring Framework](), [ASP.NET](), [Java](), [web applications](), [JavaScript](), [Programming](), [XML]() Tags: [asp-net](), [java](), [javascript](), [programming](), [spring-framework](), [web-applications](), [xml]() ### AI overview The article explains Inversion of Control (IoC) as a framework design approach in which frameworks handle common work and invoke application code when appropriate. It discusses examples in Java web applications and ASP.NET, then describes an eQube scheduler that uses XML configuration, event hooks, and JavaScript to automate reports with different filter configurations. ### Source excerpt This morning I started reading about the Spring Framework and, as usual, I followed a rabbit hole to learn what the phrase Inversion of Control (IoC) means. IoC is also known as the Hollywood Effect ("don't call us, we'll call you"). A lot of programming frameworks use an inversion of control to take care of the bulk of the work and leave your code to perform its task (and only its task).Most web frameworks are a good example of IoC. In Java web applications, the framework takes care of all HTTP complexities and turns control over to your servlet or JSP when the time is right. This leaves your JSP to process the request and return a response - easy! The ASP.NET framework has an excellent inversion of control with its postback model. The framework allows for applications to be built very similar to Windows applications - the underlying framework takes care of display issues and calls parts of the applications code when the time is right. A lot of these calls to code are handlers for events like Click, Load, and others.As I read about this "new" concept I began to realize that it wasn't new at all. ASP.NET and J2EE use it extensively. In fact, I have created such a framework without realizing what I created. In the middle of last year I created a pluggable scheduler interface for our eQube environment that allows the programmer to simply specify report names and filter values via XML, and when it comes time to do something special, the programmer can hook into events and have the framework execute some JavaScript code to do something special.I stumbled into creating this framework after doing several short projects that required some boilerplate code to interface with the eQube APIs. It all happened quite innocently, but having taken the incidental route to IoC framework I have gotten much more value than I thought I would. For instance, it is suddenly very easy to run a report with 400 different filter configurations. I just put together some XML to spec the report a