JavaPro on foojay.io - Friends Of OpenJDK

One Base URL, Many Coding Agents: What an OpenAI-Compatible Gateway Looks Like From java.net.http

Wed, 09 Sep 2026 16:09:53 +0000

Somewhere in every coding agent there is an HTTP client. Claude Code, Codex, Cursor, Cline, OpenCode: strip away the terminal UI or the editor pane and each of them serializes a conversation into JSON, POSTs it to a base URL with an API key in a header, and streams the answer back. The client owns the prompt assembly, the tool loop and the rendering; the model sits on the far side of that socket.

Debugging Is Invariant Discovery: What One Kafka Session Taught Us About AI Agents

Tue, 08 Sep 2026 14:14:36 +0000

Every Java team has a sentence like this one somewhere:

Any operation on a TID must go through the single asynchronous path and must not let TMS and EMV drift apart.

It is the kind of rule that is obvious once said and invisible until then. A terminal ID (TID) in a payments system, an asynchronous pipeline that updates two downstream systems, and the requirement that the two never disagree. Nothing in the type system enforces a rule like that, and no single class owns it. Rules of this kind live between consumers, services and stores.

“Commit created” — but it isn’t: why the agent’s word needs external verification, and what the mistake costs

Tue, 08 Sep 2026 08:54:03 +0000

A detailed report reads like proof. The agent lists the files it touched, names the branch, quotes a commit hash, adds a test count and closes with “done”. The work has a shape. The shape looks right. You have six more tickets.

The report is model output. The commit, if it exists, lives in .git. The file, if it exists, lives on disk. The build result lives in a process exit code and a run log. The chat window is none of those places, and it can only vouch for itself.

Did Your AI Agent Ever Run a Debugger? One JVM Bug, Two Agent Runs

Thu, 03 Sep 2026 13:48:32 +0000

Java developers reach for the debugger without thinking about it. Set a breakpoint, run the failing test, look at the variables, then decide what to change.

Most AI coding agents I have watched skip that step. They read the stack trace, read the source, and propose a patch. The reasoning can look excellent and still be a guess about a program nobody ran.

I wanted to know what that guess costs. So I took one real JVM bug, one model, one prompt, and ran it twice with two debugging workflows. Here is what the two transcripts show.

Scoped Values: Why I Banned ThreadLocal in Exeris

Thu, 28 May 2026 09:36:00 +0000

In a zero-copy runtime designed for 1-VT-per-Stream density, ThreadLocal is a performance serial killer. Here is the forensic analysis and how JEP 506 Scoped Values changed everything.

When I started designing the Exeris Kernel — a next-generation, zero-copy runtime built for Java 26+ — I established one non-negotiable architectural law: “No Waste Compute.”

In a system designed to handle extreme density by mapping exactly one Virtual Thread to every network stream (1-VT-per-Stream), every byte of memory and every CPU cycle must be intentional.

Foojay Podcast #94: More Than a Blog: How Foojay Connects, Sustains, and Evolves the Java Community

Mon, 04 May 2026 06:26:00 +0000

Foojay.io, the website for the Friends Of OpenJDK, is turning six years old. To celebrate, Frank Delporte headed to JCON in Cologne, Germany, and sat down with twelve members of the Java community to talk about what Foojay means to them, what they learn from each other, and how the community is evolving.

This episode covers a lot of ground. Sharat Chandar reflects on 25 years in the Java community and why the people are what keep the language alive. Markus Westergren and Iryna Dohndorf both focus on a theme that comes up again and again: developer sustainability. Not just green software, but how you stay healthy, grounded, and relevant when AI is changing everything around you. Markus and his wife researched how developers are reacting to AI, from ignoring it completely to transforming everything they do. Iryna talks about building resilience and robustness as skills, not afterthoughts.

Announcing bx-ldap: Enterprise LDAP for BoxLang

Tue, 16 Dec 2025 17:01:13 +0000

We’re excited to announce the release of bx-ldap, a comprehensive LDAP module that brings enterprise-grade directory access to BoxLang! This module goes above and beyond traditional CFML LDAP implementations, offering modern features like connection pooling, event-driven programming, multiple return formats, and a clean, intuitive API.

Note: bx-ldap is a premium module available exclusively to BoxLang +/++ subscribers.

🎯 Why?

Whether you’re integrating with Active Directory, OpenLDAP, or any LDAP-compliant directory service, bx-ldap makes it simple and powerful. From basic queries to complex directory operations, this module handles it all with grace and performance.

From Reactive Streams to Virtual Threads

Mon, 07 Apr 2025 19:34:45 +0000

Virtual Threads deliver a fast, cheap (in terms of memory & switching speed) threading solution for the JVM.

They promise the return of a direct-style, synchronous programming model.

But is that enough to challenge the status quo regarding data streaming?

Can we have the best of both worlds: the simplicity that Virtual Threads promise and the resilience and safety of Reactive Streams?

Let’s find out, on JavaPro, here:

From Reactive Streams to Virtual Threads