#java

JavaFX In Action #27 with David Gutierrez about JMathAnim to Create Mathematical Animations · webtechie.be

JMathAnim là thư viện JavaFX do nhà toán học David Gutierrez phát triển, cho phép tạo các hình ảnh toán học động và xuất ra video. Thư viện hỗ trợ hoạt ảnh công thức LaTeX, hình học, fractal và lý thuyết số, tích hợp trình soạn thảo mã Ruby, highlighting cú pháp, render LaTeX và xuất video. Gutierrez xây dựng nó trong thời gian giãn cách COVID mà không có nền tảng kỹ thuật phần mềm truyền thống.

Nếu bạn muốn khám phá cách kết hợp toán học với lập trình để tạo ra những biểu diễn động thú vị cho giáo dục hoặc nghiên cứu, JMathAnim sẽ là nguồn tư liệu hữu ích để bạn học cách xây dựng các animation toán học chuyên nghiệp từ JavaFX.

Hardwood 1.0: A Fast, Lightweight Apache Parquet Reader for the JVM

Hardwood 1.0 is a new Apache Parquet reader library for the JVM, built from scratch with no mandatory dependencies and multi-threaded page decoding by default. It targets Java 21+, is Apache 2.0 licensed, and available on Maven Central. The library offers two APIs: a row reader for ergonomic record access and a column reader for high-throughput analytical workloads. Benchmarks show Hardwood achieving 16.5M rows/sec on 8 vCPUs vs parquet-java's single-threaded approach, with consistent advantages in both full scans and predicate push-down scenarios. A CLI tool with an interactive TUI (hardwood dive) is also included, with native binaries for Linux, macOS, and Windows. Upcoming work includes Parquet write support in 1.1, Bloom filter support, encryption, and Apache Flink integration.

adam bien's blog

SBCE là phương pháp phát triển theo đặc tả (spec-driven) tích hợp trực tiếp đặc tả vào file package-info.java của Java thông qua JEP 467 Markdown comments (///). Phương pháp này hoạt động ở hai chế độ: 'new' để viết đặc tả và 'apply' để điều chỉnh code cho đến khi test pass, không cần CLI hay dependencies, nhằm phục vụ AI agents theo kiến trúc bce.design.

Lập trình viên nên đọc bài này để khám phá cách tích hợp quy định kỹ thuật trực tiếp vào mã nguồn bằng cách sử dụng Javadoc, giúp giảm thiểu sự trùng lặp và tối ưu hóa quá trình phát triển bằng cách loại bỏ các file spec riêng biệt.

Azul wants to find your unpatched JVMs before AI does

Azul Systems is offering a free JVM vulnerability risk assessment tool that scans enterprise networks to identify unpatched Java runtimes, including embedded and unmanaged instances often missed by standard asset discovery. The tool cross-references findings against the CISA KEV catalog and NVD, and produces a prioritized remediation roadmap. The pitch is tied to Azul Core, a security-only OpenJDK distribution that ships patches without new features or bug fixes, reducing breakage risk for long-running Java estates. The threat narrative centers on AI-accelerated exploit development — citing real research showing GPT-4 autonomously exploiting 87% of known critical CVEs at ~$8.80 each — but Azul's headline claim relies on Anthropic's unreleased Mythos model, which Azul's own product director admits he has never tested. The free assessment is a lead-generation tool that converts to paid Azul Core subscriptions.

Chainguard targets Java’s unpatched vulnerability backlog with drop-in remediated libraries

Chainguard has launched generally available CVE remediation for Java libraries, starting with the Spring Boot ecosystem. The offering lets teams swap vulnerable libraries for Chainguard-remediated drop-in versions by updating a single pom.xml reference. Remediated packages use a new version identifier with a -0.cgr.N suffix, making them appear clean to vulnerability scanners and auditors. Each package ships with an SBOM and provenance attestation, and is recognized by Wiz, AWS Inspector, Grype, and Trivy. The solution targets the growing backlog of unpatched CVEs in end-of-life Java frameworks — Spring Boot 2.7, for example, carries 143 unpatched CVEs — giving organizations a fourth option beyond security exceptions, DIY backports, or disruptive version upgrades.

Build a Spring Boot REST API with Amazon Aurora DSQL

A step-by-step guide to building a Spring Boot 3.3 REST API integrated with Amazon Aurora DSQL, AWS's serverless multi-region distributed SQL database. Covers configuring the Aurora DSQL JDBC Connector for IAM authentication, implementing optimistic concurrency control (OCC) with two-layer retry logic using HikariCP and Spring Retry's @Retryable with exponential backoff, and deploying the application across two AWS regions (us-east-1 and us-west-2) to demonstrate active-active multi-region writes. Includes a product inventory CRUD API example, concurrent write testing scenarios, and production considerations around observability, connection pooling, regional failover with Route 53, and IAM least-privilege security.

HeroDevs Allies with Commonhaus Foundation to Support Open Source Software

HeroDevs has joined the Commonhaus Foundation as the founding member of the Open Source Sustainability Initiative (OSSI), establishing partnerships with the Hibernate, Jackson, and Quarkus communities to provide commercial support for older, end-of-life versions of these frameworks. The initiative targets enterprise IT organizations — particularly in regulated industries — that cannot upgrade to the latest framework versions on short notice. A key driver is the growing AI-powered threat landscape, where frontier models can now discover thousands of vulnerabilities in legacy software and malicious actors can reverse-engineer exploits within hours of disclosure. HeroDevs argues that outsourcing maintenance of legacy open source components to an external provider is often more practical than replacing them with custom code, given the scale of dependencies in modern enterprise applications.

Quarkus 3.37 - Extension-based modularity, Hibernate ORM 7.4, Jackson reflection-free serializers, and more

Quarkus 3.37 has been released with several notable improvements. A new experimental quarkus-jlink extension enables extension-based modularity by producing jlink-ed custom runtime images that include only required JDK modules, reducing container image sizes. Hibernate ORM is bumped to 7.4 (with behavioral changes including SQL-level pagination limits, new NOT NULL constraints on timestamp columns, and PostgreSQL 14 minimum), Hibernate Reactive to 3.4, and Hibernate Search to 8.4. Jackson reflection-free serializers are now enabled by default for improved serialization performance. The REST Client gains RestMultiResponse for extracting status codes and headers from streamed responses. A new quarkus-rest-data-hibernate-types extension is added for better REST and Hibernate ORM integration.

Long Story Short: I Found My Place Between Code and Community

A new AI Builder Advocate at Okta introduces herself, sharing her journey from backend software developer to developer relations. She covers her technical background in Java, Spring Boot, Quarkus, Kubernetes, and Docker, her community work as a MongoDB Champion, and her excitement about the intersection of identity, security, and AI at Okta.

Vaadin 25.2: Build UIs in plain language, and call the browser from Java

Vaadin 25.2 introduces three major additions for Java-based UI development. First, AI controllers (GridAIController, ChartAIController, FormAIController) let end users build data grids, charts, and fill forms using natural-language prompts, with data never sent to the LLM for safety. Second, seven native browser APIs — Geolocation, Clipboard, Fullscreen, WakeLock, Page Visibility, WebShare, and Screen Orientation — are now accessible from server-side Java without writing JavaScript. Third, existing TestBench or Playwright end-to-end tests can be converted into Grafana k6 load tests via a Maven plugin. The release also graduates several components (Slider, Badge, Master-Detail Layout, Modular Upload) to GA, deepens Signals integration, adds security hardening (safe-by-default URLs, clickjacking protection, supply-chain delay for npm packages), and enhances Vaadin Copilot with an annotation/review workflow, customizable palette, and EU-hosted option.

What’s New In The June 2026 Azul Payara Release?

The June 2026 Azul Payara release cycle delivers updates across all supported branches (7, 6, 5, and 4). A critical CSRF and SSRF security fix in the Admin Console and REST management interface is backported to every supported version. Azul Payara 7.1.0 is the first monthly release post-GA on the Jakarta EE 11 line, shipping MicroProfile 6.1 and promoting several components (EclipseLink 5.0.0, Jersey 4.0.2, Payara Security Connectors 4.0.0) from beta/alpha to GA. Jakarta Data gains method-level @Transactional overrides and a performance fix. Payara 5.88.0 and 6.39.0 include a notable behaviour change: the server 'ready' signal now fires after post-boot configuration and application loading by default, aligning with Payara 7 behaviour. Teams relying on post-boot scripts or transaction recovery timing should review this change before upgrading.

A Guide to Agent Skills in Spring AI

Agent Skills is an open specification for defining reusable capabilities that an AI agent can invoke locally, without the overhead of running a full MCP server. A skill is a directory containing a SKILL.md manifest file with a name, description, and natural language instructions, plus any associated scripts. Spring AI 2.x supports Agent Skills via the spring-ai-agent-utils community library. The tutorial walks through creating a custom article-summarizer skill backed by a Python script, wiring it into a Spring AI ChatClient using SkillsTool, FileSystemTools, and ShellTools, and exposing it through a REST endpoint. The agent automatically matches user requests to relevant skills based on their descriptions, loads the instructions into context, and executes the associated scripts to fulfill the request.

Take Full Control of Your Query Results

BoxLang 1.14.0 introduces Query Transformers, a new feature that lets developers attach a callable (closure, class instance, or registered name) to any queryExecute() call to reshape database results in a single pass. Instead of post-processing query results with separate loops, transformers receive the raw Query object and execution metadata and return whatever format the application needs — REST envelopes with pagination, hydrated domain objects, columnar tabular data, or schema-aware result sets with full JDBC column descriptors. The release also adds getColumnMeta() to preserve JDBC ResultSetMetaData, application-level transformer registration via Application.bx, global query defaults via this.queryOptions and boxlang.json, and transformer support in the bx:query component. The feature is purely additive and requires no migration from 1.13.x.

Dynamic Authorization Scopes in Spring Authorization Server

A step-by-step guide to extending Spring Authorization Server to support dynamic OAuth 2.0 scopes — scopes not known in advance by the authorization server. Covers when dynamic scopes are useful (e.g., single-operation tokens for transfers or sensitive updates), and walks through the required customizations: scope validation logic via a custom AuthenticationValidator, consent validation using a Predicate, a custom consent page with Thymeleaf, and end-to-end integration testing with WebEnvironment.RANDOM_PORT and RestTestClient. Code separates Spring-specific adapter code from business logic via a DynamicScopeService.

Introducing Vaadin Enterprise Edition

Vaadin has launched Vaadin Enterprise Edition (Vaadin EE), a dedicated product tier for organizations building long-lived, business-critical Java applications. It adds support for enterprise application servers (WebSphere Liberty, JBoss EAP, Payara Enterprise, Spring Enterprise), maintained OpenRewrite upgrade recipes for smoother version migrations, and formal assurances including security review certificates, VPAT accessibility reports (WCAG 2.1 AA, Section 508, EN 301 549), ISO certification, first-line CVE fixes, and 15 years of maintenance per major release. An air-gapped MCP server is included for teams in restricted or regulated environments. Vaadin EE is available starting with the Vaadin 25.2 release on June 24, 2026, and is aimed at enterprises rather than individual developers.

SwingBridge 1.2: Java Swing and Vaadin, now talking to each other

SwingBridge 1.2 cho phép giao tiếp hai chiều giữa Java Swing và Vaadin thông qua các phương thức Java đơn giản, quản lý luồng tự động giữa Swing EDT và Vaadin UI thread. Phiên bản mới hỗ trợ ứng dụng NetBeans RCP, cải thiện khả năng phản hồi của canvas trình duyệt, cập nhật lên nền tảng Vaadin mới nhất và cung cấp xử lý lỗi rõ ràng hơn khi khởi chạy ứng dụng Swing thất bại.

Lập trình viên phát triển ứng dụng đa nền tảng sẽ tìm hiểu SwingBridge 1.2 để tối ưu hóa giao diện người dùng trên cả môi trường desktop Swing và web Vaadin mà không gặp rủi ro deadlock và cần thiết cho các dự án hỗ trợ cả hai nền tảng.

Java’s SSLContext protocol name is a footgun

Java's SSLContext.getInstance() method has a counterintuitive and dangerous behavior: specifying a TLS version like "TLSv1.2" does not set a minimum version as the documentation implies — it actually sets a maximum version, silently capping the connection to that version and below. This means developers who follow common advice to specify a version string may unknowingly be implementing a self-inflicted protocol downgrade attack. The behavior is present in both the default SunJSSE provider and Android's Conscrypt/BoringSSL provider. The recommended workaround is to use the generic "TLS" identifier instead, which modern JDK implementations interpret as supporting TLS 1.2 and 1.3. The issue affects client-side connections only; server-side contexts ignore the version parameter entirely.

Systematic AI Coding: My Takeaways from the Eclipse Foundation Workshop in Brussels

A developer's takeaways from the Eclipse Foundation's first AI Coding Workshop in Brussels, led by Jonas Helming. The core message is moving from 'vibe coding' (prompt and hope) to 'Systematic AI Coding' — understanding how coding agents actually work and building repeatable workflows around them. Key insights include: LLMs are stateless and context is everything; efficiency degrades around 40% of context window capacity (the 'dumb zone'); time allocation shifts dramatically with AI (more design/review/debugging, less typing); and 'done' from an agent doesn't mean production-ready. Practical workflow advice covers when to start fresh sessions, how to compact context manually, and the importance of upfront design before prompting. The Eclipse Foundation's Open VSX and Theia IDE are also briefly highlighted.

Quarkus Unpacked: Insights from the Foojay Podcast

A Q&A-style writeup from a Foojay podcast episode covering Quarkus in depth. Topics include how Quarkus compares to Spring Boot and Micronaut, its build-time optimization approach (vs JIT and AOT), live reload and Dev Mode features, JVM vs native compilation trade-offs, cloud cost reduction through resource density and scale-to-zero, and how Vert.x and Virtual Threads work together. The post also covers observability with OpenTelemetry, security via OIDC/WebAuthn extensions, and the Quarkiverse extension ecosystem.

Client-Side Load Balancing at a Million Requests Per Second

Zalando's engineering team built an in-process client-side load balancer (CSLB) to handle over a million requests per second of internal fan-out traffic for their Product Read API, replacing shared Skipper ingress hops. The implementation replicates Skipper's xxHash64 consistent-hash ring for cache locality, uses a Kubernetes watch-based informer for pod discovery, and adds N-ring fade-in to prevent cold-cache spikes on scale-up. A key innovation is occupancy-based bounded load using Little's Law (seconds of work per second) rather than in-flight counts or throughput, combined with a latency multiplier borrowed from Finagle. Results include eliminating Skipper's fleet from 50+ pods to 8, reducing their own pod fleet by 25%, and saving over $1,000/day. AZ-aware routing was prototyped but paused due to edge cases around bounded-load threshold miscalculation during dual fade-in. The post also covers pipeline improvements, retry hardening, FIFO buffering, and how detailed logging revealed mysterious node-level network freezes that had previously been invisible.