---
title: "Java Weekly, Issue 659"
url: https://daily.dev/posts/java-weekly-issue-659-peioe1xl3
source_url: https://feeds.feedblitz.com/~/967864352/0/baeldung
type: article
source: "Baeldung"
published: 2026-08-15T10:33:25.546Z
updated: 2026-08-15T10:33:48.668Z
tags: ["java", "spring", "gradle", "jdk"]
reading_time: 3
upvotes: 4
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Java Weekly, Issue 659

**[Baeldung](https://daily.dev/sources/baeldung)** · 3 min read · 4 upvotes · 0 comments

## Summary

A weekly roundup for Java developers covering evolving an MCP server across specification upgrades, Project Valhalla's first preview (JEP 401) redefining == semantics for value objects, plus curated links on JVM security, DuckDB in Spring Batch, JDK Flight Recorder profiling, post-quantum cryptography in LTS JDK releases, IntelliJ IDEA AI agent features, HTTP extension design research, and a batch of library/tool version updates (IntelliJ IDEA 2026.2.1, Gradle 9.7.0, Vert.x 4.5.32, Elasticsearch, Camel, Zuul).

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://feeds.feedblitz.com/~/967864352/0/baeldung>

## Questions this post answers

### What does JEP 401 change about how == works for Java objects?

JEP 401, part of Project Valhalla's first preview, introduces identity-free value classes and records where == comparisons behave differently than for identity classes. Identity classes retain the traditional reference-based equality semantics, while value objects get value-based comparison, changing long-standing assumptions about what == means for a given class.

_Track how Valhalla's value classes reshape equality checks in your Java codebase, discussed on daily.dev._

### How can I keep older clients working while upgrading a Java MCP server to a new protocol specification?

Use header-based routing combined with a temporary adapter layer so a Helidon-based Java MCP server can serve both stateless and older protocol paths simultaneously. Tests exercise both protocol paths during the transition, allowing a gradual migration without breaking existing client integrations as the MCP specification evolves.

_Developers navigating MCP spec upgrades can follow evolving server patterns like this on daily.dev._

## Similar posts on daily.dev

- [Java Weekly, Issue 644](https://daily.dev/posts/java-weekly-issue-644-on1iz12bc) · Baeldung · 5 upvotes · 0 comments

---

Tags: [#java](https://daily.dev/tags/java), [#spring](https://daily.dev/tags/spring), [#gradle](https://daily.dev/tags/gradle), [#jdk](https://daily.dev/tags/jdk)

[View this post on daily.dev](https://daily.dev/posts/java-weekly-issue-659-peioe1xl3)