- Spring Boot's Hidden Secret for Configuration: EnvironmentPostProcessor
Spring Boot's Quiet Hook for Shipping Configuration: EnvironmentPostProcessor
Hi everyone! This is Mikhail Polivakha, technical lead of the Axelix project (an open-source product that helps you find common problems and inefficiencies in Spring Boot applications — btw, give us a star!).
I want to talk about a piece of Spring Boot that a lot of people have never touched directly, yet almost everyone has bumped into the problem it solves. Let me start with a scene that I suspect will feel familiar:
- Building an AI-Powered Code Review Assistant in Java
Code review is the highest-leverage activity on most engineering teams, yet it is also the most expensive in terms of senior-developer time. What if you could offload a first pass to an LLM that understands Java idioms, common anti-patterns, SOLID principles, and security pitfalls — and get back structured, actionable feedback before a human even opens the PR?
In this post, we will build exactly that: a self-contained Java application that accepts a Java source snippet, sends it to an LLM (OpenAI GPT-4o or a locally running Ollama model — your choice), and returns a structured list of code-quality findings with severity levels and suggested fixes.
- Modernizing a Legacy Java Application With OpenRewrite: What We Automated and What We Didn't
OpenRewrite in a Real Enterprise Migration
Recently, we modernized a 9-year-old enterprise application that involved two major changes happening together:
- Java 8 â†' Java 25
- Spring Boot 2.3.3 â†' Spring Boot 3.3.4
At the same time, we were also moving the application from a monolithic architecture toward microservices.
- From Database Changes to Real-Time Actions at Scale: Oracle GoldenGate and Java
DB changes can be streamed in real time via Oracle GoldenGate. Java applications can then consume them to validate/act on/route events without polling the DB.
Goal
Listen to real-time transactions in the DB, act on all operations within transactions, and maintain transaction boundaries with near real-time SLAs.
- Persisting Cookies Across JAX-WS Service Calls Using a Custom SOAP Handler
The Cookie That Never Came Back
The first call authenticated the user. The second failed.
I was integrating with a customer-provided SOAP service exposed through a single WSDL, with JAX-WS client classes generated by IBM Rational Application Developer from the WSDL and its XSDs. The first call authenticated the user and came back with a Set-Cookie header. Every call after it needed that cookie. The generated client sent none of it. Each invocation behaved as an independent conversation, and the workflow broke on its second step. No exception, no warning. Just a server that had forgotten who you are.