<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spring AI on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/spring-ai/</link><description>Recent content in Spring AI on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 16 Jul 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/spring-ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Solving Spring AI's UI Challenge with AG-UI's Java SDK</title><link>https://javapro-en.svenruppert.com/solving-spring-ais-ui-challenge-with-ag-uis-java-sdk/</link><pubDate>Thu, 16 Jul 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/solving-spring-ais-ui-challenge-with-ag-uis-java-sdk/</guid><description>&lt;h2 id="introduction-the-missing-link-in-java-ai-development"&gt;Introduction: The Missing Link in Java AI Development&lt;/h2&gt;
&lt;p&gt;Ask any Java developer who has tried to build an AI feature in a production application and they&amp;rsquo;ll tell you the same thing: the backend isn&amp;rsquo;t the hard part anymore. Spring AI makes it easy to invoke an LLM, define prompts, and create tools. But turning these interactions into a smooth, interactive user experience? That&amp;rsquo;s where the struggle begins.&lt;/p&gt;
&lt;p&gt;Most developers solve this by inventing custom message formats, WebSocket events, and ad-hoc rules for how the UI should render tool calls. Each application reinvents the bridge between frontend interactions and agent intelligence. The result? A fragile, inconsistent layer that must be rebuilt for every project.&lt;/p&gt;</description></item><item><title>From Prototype to Production: Building Safe and Reliable AI Agents with Spring AI and MCP</title><link>https://javapro-en.svenruppert.com/from-prototype-to-production-building-safe-and-reliable-ai-agents-with-spring-ai-and-mcp/</link><pubDate>Thu, 25 Jun 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/from-prototype-to-production-building-safe-and-reliable-ai-agents-with-spring-ai-and-mcp/</guid><description>&lt;p&gt;The AI agent demo works perfectly in the development environment. Your prototype handles natural language queries, executes tool calls, and generates sensible responses. But when stakeholders ask &amp;lsquo;Can we deploy this?&amp;rsquo;, reality sets in. That question exposes the massive gap between a functional prototype and a Spring AI production system ready for real traffic, unexpected failures, and business-critical operations.&lt;/p&gt;
&lt;p&gt;That question reveals the massive gap between a working prototype and a production system. The demo doesn&amp;rsquo;t handle failures gracefully. It has no guardrails against harmful outputs. There&amp;rsquo;s no visibility into what the agent is actually doing. Cost per request? Unknown. Error rates? No idea. Recovery strategy when the LLM provider goes down? Haven&amp;rsquo;t thought about it.&lt;/p&gt;</description></item><item><title>Building Production-Ready AI Agents with Java and Spring AI</title><link>https://javapro-en.svenruppert.com/building-production-ready-ai-agents-with-java-and-spring-ai/</link><pubDate>Thu, 30 Apr 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/building-production-ready-ai-agents-with-java-and-spring-ai/</guid><description>&lt;p&gt;Java developers have been building enterprise applications for decades, but when it comes to AI, the conversation has been dominated by Python. &lt;a href="https://spring.io/projects/spring-ai"&gt;Spring AI&lt;/a&gt; changes this situation. It brings the same patterns we know from Spring - dependency injection, auto-configuration, portable abstractions - to AI development.&lt;/p&gt;
&lt;p&gt;In January 2026 we built a sample agent application, and we want to share what we learned. The sample AI agent handles conversations with memory, answers questions from internal knowledge bases, uses external APIs, and integrates with existing microservices - all running on &lt;a href="https://aws.amazon.com/bedrock/"&gt;Amazon Bedro&lt;/a&gt;&lt;a href="https://aws.amazon.com/bedrock/"&gt;ck&lt;/a&gt;. If you want to try it yourself, the &lt;a href="https://catalog.workshops.aws/java-spring-ai-agents"&gt;Building AI Agents with Java and Spring AI&lt;/a&gt; workshop [1] walks you through typical challenges of Generative AI models and provides step by step solutions with code available on &lt;a href="https://github.com/aws-samples/java-on-aws"&gt;GitHub&lt;/a&gt; [2].&lt;/p&gt;</description></item><item><title>Building MCP Tools (for AI Agents) using Spring AI</title><link>https://javapro-en.svenruppert.com/building-mcp-tools-for-ai-agents-using-spring-ai/</link><pubDate>Wed, 07 Jan 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/building-mcp-tools-for-ai-agents-using-spring-ai/</guid><description>&lt;h2 id="introduction"&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;The innovation of AI Agents and Agentic AI systems has revolutionized the adoption of Generative AI. Agents empower systems to autonomously achieve goals by performing tasks. &lt;strong&gt;Tools&lt;/strong&gt; are the key building blocks for AI agents that provide them with superior decision-making and implementation capabilities. &lt;strong&gt;Model Context Protocol (MCP)&lt;/strong&gt; protocol has standardized the approach of building tools enabling faster, seamless integration. In this paper, we are going to talk about MCP, the underlying architecture. We will also provide a simple code example of building MCP tools in Java using Spring AI and integrating it with an AI Agent.&lt;/p&gt;</description></item></channel></rss>