<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Loïc Magnette on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/lo%C3%AFc-magnette/</link><description>Recent content in Loïc Magnette on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 08 Jul 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/lo%C3%AFc-magnette/index.xml" rel="self" type="application/rss+xml"/><item><title>LangChain4j Agentic Workflows: From AI Calls to Multi-Agent Systems in Java</title><link>https://javapro-en.svenruppert.com/langchain4j-agentic-workflows-from-ai-calls-to-multi-agent-systems-in-java/</link><pubDate>Wed, 08 Jul 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/langchain4j-agentic-workflows-from-ai-calls-to-multi-agent-systems-in-java/</guid><description>&lt;p&gt;You have built AI features into your Java application. Your model is wrapped in a service, RAG is feeding it context, tools are wired, and calls are flowing. It works. Then requirements evolve. A single prompt-and-response is no longer enough. You need steps that follow each other, branches based on decisions, retries when things fail, and multiple actions running concurrently. The question shifts from &amp;ldquo;how do I call an LLM?&amp;rdquo; to &amp;ldquo;how do I orchestrate multiple LLM-driven tasks into a coherent system?&amp;rdquo;&lt;/p&gt;</description></item><item><title>A2A Building Interoperable AI Agents with Java</title><link>https://javapro-en.svenruppert.com/a2a-building-interoperable-ai-agents-with-java/</link><pubDate>Wed, 18 Mar 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/a2a-building-interoperable-ai-agents-with-java/</guid><description>&lt;p&gt;&lt;a href="https://schedule.jcon.one/2026/session/1052858"&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2026/03/2026-Magazin-Artikel-Banner-1024x213.png" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="why-agents-need-friends"&gt;Why agents need friends?&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;ve recently seen a boom in AI &amp;ldquo;agents&amp;rdquo;. AI Agents are usually described as a service that talks to an AI model to perform some kind of goal-based operation using tools and context it assumes.&lt;/p&gt;
&lt;p&gt;But most of these agents are still working in an isolated environment. You build an agent into your application and it offers some capabilities, but that&amp;rsquo;s it. You&amp;rsquo;re basically building a monolith with AI in it.&lt;/p&gt;</description></item><item><title>Bridging the Gap: Full-Stack Development Without the Headaches</title><link>https://javapro-en.svenruppert.com/bridging-the-gap-full-stack-development-without-the-headaches/</link><pubDate>Tue, 06 May 2025 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/bridging-the-gap-full-stack-development-without-the-headaches/</guid><description>&lt;p&gt;Working on web projects often means dealing with two separate environments—one for the backend and another for the frontend—each with its own ecosystem. Developers frequently run into issues when dealing with the ecosystem of their counterpart, creating a needless wall between front-end and back-end developers. You have to use unfamiliar tools, follow API changes, create mocks, and have a hard time creating e2e tests. Overall, this makes development unnecessarily frustrating and a time-consuming process.&lt;/p&gt;</description></item><item><title>AI-Powered Form Wizards: Chat, Click, Done</title><link>https://javapro-en.svenruppert.com/ai-powered-form-wizards-chat-click-done/</link><pubDate>Tue, 15 Apr 2025 10:00:23 +0000</pubDate><guid>https://javapro-en.svenruppert.com/ai-powered-form-wizards-chat-click-done/</guid><description>&lt;p&gt;&lt;a href="https://schedule.jcon.one/session/794986"&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2025/04/Magazin-Artikel-Banner-2-1024x214.jpg" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="transforming-form-filling-into-a-conversational-experience"&gt;Transforming Form Filling into a Conversational Experience&lt;/h2&gt;
&lt;p&gt;Forms are everywhere—tax declarations, job applications, or even signing up for a new service. Although some forms are simple, many include ambiguous fields, complicated logic, or subpar design. This may frustrate users and make them more likely to make mistakes. Completing paperwork shouldn&amp;rsquo;t be like solving a puzzle&lt;/p&gt;
&lt;p&gt;Traditional forms, with their rigid structures and often confusing layouts, present a significant hurdle for users. Our objective was to dismantle this static paradigm and replace it with a dynamic, conversational interface. Instead of forcing users to navigate a pre-defined maze of fields, we envisioned an interactive experience where an AI assistant adapts in real-time. This approach fundamentally shifts the burden of data entry and validation. A user chatting with an AI can dramatically reduce errors and streamline the overall process. Imagine a conversation, not a questionnaire, where the AI guides you through each step.&lt;/p&gt;</description></item></channel></rss>