fidzu : jboss

The talks and speakers have now been announced for Keycloak's Identity Summit. Save your spot today! 📍 - taking place in Amsterdam on August 28th, 2025! This year's edition of the Keycloak Identity Summit promises more content, more connections, and even more opportunities to engage with the people shaping the future of identity and access management. TALK HIGHLIGHTS Our talks highlight the broad spectrum of the Keycloak ecosystem: How to run it with confidence and securely, how extend it, and how to apply it in existing and new scenarios. See below for a short-list of topics we cover: * Human and Workload Identities: Bridging the Gap with Keycloak * AI Meets Identity: Managing Keycloak with Natural Language via MCP * Observability in Keycloak: Where Does It Hurt? * The Event Sorcerer with the Keycloak: The Battle against Dynamic Configuration * Protectors of the Realm: Breaking and Fixing Keycloak Configurations A GREAT PLACE TO NETWORK Networking lunch Our extended lunch break is designed to help you meet fellow attendees, swap ideas, and build meaningful professional connections in a relaxed setting. Meet the maintainers We will have a panel discussion with the maintainers. Ask your questions live and get a response from the experts! Business drinks Stick around after the last session for informal networking over drinks. Want to sponsor this year's Business Drink? Get in touch with us-we'd love to partner with you! GET YOUR TICKET AND JOIN US! Whether you're a developer, architect, security specialist, or product owner, KEYCONF25 is your opportunity to gain knowledge, grow your network, and contribute to the future of the Keycloak community. 📅 August 28th, 2025 📍 Amsterdam, Netherlands Tickets are now available at - secure your spot! WANT TO GET INVOLVED? Let's continue building a stronger, smarter IAM community-together. We can't wait to see you in Amsterdam!

27 Jun 2025 12:00am GMT

The agent revolution just took a massive leap forward! Following the recent landmark that Google has donated the Agent2Agent (A2A) protocol to the Linux Foundation, we're thrilled to announce the launch of the , created by the WildFly and Quarkus teams in close collaboration, and now contributed to the official A2A project. A NEW ERA UNDER LINUX FOUNDATION STEWARDSHIP The protocol's transition to the Linux Foundation represents more than just a change of governance: it's a commitment to vendor-neutral, community-driven innovation. Similar how WildFly and Quarkus both recently joined the CommonHaus foundation. This ensures that A2A, as a critical interoperability standard, remains open and accessible to all. With more than 100 companies now supporting the protocol, we're witnessing the formation of what industry leaders are calling "an open, interoperable Internet of Agents." With the A2A Java SDK now part of this movement, enterprise developers can participate in this open agent ecosystem from day one. WHY JAVA SDK MATTERS Here's where things get exciting from a technical perspective: true polyglot agent ecosystems. The agent landscape has been fragmented, with Python dominating AI/ML workflows, JavaScript powering web-based agents, and Java serving as the backbone of enterprise backend systems. Siloed development across language ecosystems has held back the true potential of agentic applications. Our Java SDK shatters these barriers by implementing the A2A protocol specification natively in Java, enabling: * Enterprise-grade agent integration with existing Java infrastructure * Seamless interoperability between Java agents and those written in Python, JavaScript, or any A2A-compatible language with well-tested enterprise capabilities (including observability, security… ) And you know what? Writing agents in Java is now as easy as writing 1. A CLASS THAT CREATES AN A2A AGENT CARD import io.a2a.spec.AgentCapabilities; import io.a2a.spec.AgentCard; import io.a2a.spec.AgentSkill; import io.a2a.spec.PublicAgentCard; ... @ApplicationScoped public class WeatherAgentCardProducer { @Produces @PublicAgentCard public AgentCard agentCard() { return new AgentCard.Builder() .name("Weather Agent") .description("Helps with weather") .url("http://localhost:10001") .version("1.0.0") .capabilities(new AgentCapabilities.Builder() .streaming(true) .pushNotifications(false) .stateTransitionHistory(false) .build()) .defaultInputModes(Collections.singletonList("text")) .defaultOutputModes(Collections.singletonList("text")) .skills(Collections.singletonList(new AgentSkill.Builder() .id("weather_search") .name("Search weather") .description("Helps with weather in city, or states") .tags(Collections.singletonList("weather")) .examples(List.of("weather in LA, CA")) .build())) .build(); } } 2. A CLASS THAT CREATES AN A2A AGENT EXECUTOR import io.a2a.server.agentexecution.AgentExecutor; import io.a2a.server.agentexecution.RequestContext; import io.a2a.server.events.EventQueue; import io.a2a.server.tasks.TaskUpdater; import io.a2a.spec.JSONRPCError; import io.a2a.spec.Message; import io.a2a.spec.Part; import io.a2a.spec.Task; import io.a2a.spec.TaskNotCancelableError; import io.a2a.spec.TaskState; import io.a2a.spec.TextPart; ... @ApplicationScoped public class WeatherAgentExecutorProducer { @Inject WeatherAgent weatherAgent; @Produces public AgentExecutor agentExecutor() { return new WeatherAgentExecutor(weatherAgent); } private static class WeatherAgentExecutor implements AgentExecutor { private final WeatherAgent weatherAgent; public WeatherAgentExecutor(WeatherAgent weatherAgent) { this.weatherAgent = weatherAgent; } @Override public void execute(RequestContext context, EventQueue eventQueue) throws JSONRPCError { TaskUpdater updater = new TaskUpdater(context, eventQueue); // mark the task as submitted and start working on it if (context.getTask() == null) { updater.submit(); } updater.startWork(); // extract the text from the message String userMessage = extractTextFromMessage(context.getMessage()); // call the weather agent with the user's message String response = weatherAgent.chat(userMessage); // create the response part TextPart responsePart = new TextPart(response, null); List> parts = List.of(responsePart); // add the response as an artifact and complete the task updater.addArtifact(parts, null, null, null); updater.complete(); } @Override public void cancel(RequestContext context, EventQueue eventQueue) throws JSONRPCError { Task task = context.getTask(); if (task.getStatus().state() == TaskState.CANCELED) { // task already cancelled throw new TaskNotCancelableError(); } if (task.getStatus().state() == TaskState.COMPLETED) { // task already completed throw new TaskNotCancelableError(); } // cancel the task TaskUpdater updater = new TaskUpdater(context, eventQueue); updater.cancel(); } private String extractTextFromMessage(Message message) { StringBuilder textBuilder = new StringBuilder(); if (message.getParts() != null) { for (Part part : message.getParts()) { if (part instanceof TextPart textPart) { textBuilder.append(textPart.getText()); } } } return textBuilder.toString(); } } } Pretty straightforward, right? The SDK provides all the necessary components to create agent cards, handle agent execution, and manage communication between agents. Note: In future some of this boiler plate code we expect will be simplified by Quarkus and other frameworks using the A2A Java SDK. And when it comes to client-side development, it's even easier. The SDK includes a simple A2A client that allows you to interact with A2A agents using the A2A protocol. This client abstracts away the complexities of the protocol, making it easy to send messages, receive responses, and manage agent interactions. Creating an A2A client in Java is as simple as: 1. CREATE AN A2A CLIENT // Create an A2AClient (the URL specified is the server agent's URL, be sure to replace it with the actual URL of the A2A server you want to connect to) A2AClient client = new A2AClient("http://localhost:1234"); 2. SEND A MESSAGE TO THE A2A SERVER AGENT // Send a text message to the A2A server agent Message message = A2A.toUserMessage("tell me a joke"); // the message ID will be automatically generated for you MessageSendParams params = new MessageSendParams.Builder() .message(message) .build(); SendMessageResponse response = client.sendMessage(params); Note that A2A#toUserMessage will automatically generate a message ID for you when creating the Message if you don't specify it. You can also explicitly specify a message ID like this: Message message = A2A.toUserMessage("tell me a joke", "message-1234"); // messageId is message-1234 And the SDK also provides a convenient way to handle task management, allowing you to create, get the current state, and cancel tasks with ease. This is especially useful for managing long-running operations or coordinating complex workflows between multiple agents. You can find more details about task management and many other features in the repository's. You just want more code? Are you interested to see interoperability in action? Explore our which demonstrates how Python and Java agents collaborate seamlessly. See this picture for a bird-eye overview, and checkout the code for more insights TECHNICAL EXCELLENCE: THE MUTINY-ZERO ADVANTAGE And if you need your agent to be reactive, don't worry about the dependencies you are adding, because the Java SDK leverages mutiny-zero as its reactive foundation, a decision that reflects our commitment to framework-agnostic excellence. is a minimal API for creating reactive streams-compliant publishers that weighs less than 50K and have zero external dependencies beyond the Reactive Streams API. This architecture delivers several compelling advantages: * No Vendor Lock-in: No specific technology commitments for your agents. * Lightweight Performance: Faster startups, reduced resource consumption. * Maximum Compatibility: Seamless integration with existing Java reactive ecosystems. * Future-Proof Design: Ready for Java's modern Flow APIs, backward compatible. This reactive foundation ensures your Java agents can handle high-throughput, low-latency agent-to-agent communications while remaining lightweight and composable. COMMUNITY-DRIVEN INNOVATION What started as an external contribution has now become an official part of the A2A project repository, showcasing how the ecosystem can rapidly evolve through diverse contributions. This is precisely the kind of collaborative development that will accelerate A2A adoption and innovation. Ready to dive in? Here's your roadmap: 1. Explore the SDK: Visit to examine the implementation 2. Study Real Examples: Check out the to see interoperability in action 3. Join the Community: Connect with fellow developers in the A2A ecosystem 4. Start Building: Begin prototyping your first multi-language agent team THE BIGGER PICTURE: COLLABORATIVE INTELLIGENCE The A2A protocol aims to break down the silos that currently limit the potential of AI infuse applications by providing a common language for AI agents to discover each other's capabilities, securely exchange information, and coordinate complex tasks. With Java now joining Python and JavaScript in the A2A ecosystem, we're building towards a future where intelligence is truly collaborative, where the most sophisticated AI systems are assembled from specialized agents, each optimized for specific tasks but unified through standardized communication protocols. This Java SDK launch is just the beginning. The A2A project under Linux Foundation stewardship is positioned for rapid expansion, with additional language implementations, enhanced security features, and enterprise-grade tooling on the horizon. Your contributions matter. Whether you're fixing bugs, adding features, creating examples, or building integrations with other frameworks - every commithelps build this collaborative future. The agent revolution is here, and with the A2A Java SDK, the entire Java ecosystem can participate. Let's build something amazing together! 🚀

27 Jun 2025 12:00am GMT

We're excited to announce the release of WildFly 37.0.0.Beta1! This beta release, available for download from , includes new features and several enhancements, alongside numerous component upgrades. KEY HIGHLIGHTS IN THIS BETA RELEASE: NEW FEATURES: * Artemis commit-interval attribute for scaledown: WildFly 37 Beta 1 exposes the Artemis commit-interval attribute for scaledown. * The /core-service=platform-mbean resources have been evolved to expose new platform MXBeans, attributes and operations. ENHANCEMENTS: * The tasks-jsf quickstart now uses Glow. * GPG detached signatures are now included with uploads at release time. The following commands demonstrate how to verify the GPG signature of the WildFly distribution: $ gpg --keyserver keyserver.ubuntu.com --recv-keys E85C11F6 $ gpg --verify wildfly-37.0.0.Beta1-src.tar.gz.asc wildfly-37.0.0.Beta1-src.tar.gz gpg: Signature made Wed 25 Jun 2025 14:33:44 BST gpg: using EDDSA key 245404A11575A55D6A41107E2D52D4ACE85C11F6 gpg: Good signature from "Darran Andrew Lofthouse " [unknown] gpg: aka "Darran Andrew Lofthouse " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 2454 04A1 1575 A55D 6A41 107E 2D52 D4AC E85C 11F6 Contributors to WildFly publish their GPG keys on the , which includes the fingerprint to aid verification. COMPONENT UPGRADES: This release includes a significant number of component upgrades, ensuring WildFly remains current with the latest technologies and provides improved performance and security. Some notable upgrades include: * Vert.x to 4.5.15. * Hibernate ORM to 6.6.18.Final (and 7.0.2.Final for WildFly Preview). * Micrometer to 1.15.0. * EclipseLink to 4.0.6. * SmallRye Fault Tolerance to 6.9.1. * Apache Santuario XML Security for Java to 3.0.6. * JBoss Universe Producers to 1.3.14. * JBoss Metadata to 16.1.0.Final. * Netty to 4.1.122.Final. * Velocity Engine to 2.4.1. * WildFly Clustering to 7.0.5.Final. * Infinispan to 15.2.4.Final. * JGroups to 5.4. * Apache Artemis to 2.41.0. * WildFly Core to 29.0.0.Beta6. * HAL to 3.7.12.Final. * Byteman to 4.0.25. * JBossWS-CXF to 7.3.3.Final. * Narayana to 7.2.2.Final. * zstd-jni to 1.5.7-3. * WildFly Licenses Plugin to 2.4.2.Final. * FasterXML Jackson to 2.18.4. * SmallRye Common to 2.12.0. * Hibernate Search to 8.0.0.Final (in WildFly preview). * Weld to 5.1.6.Final and 6.0.3.Final. * Hibernate Validator to 9.0.1.Final (in WildFly preview). * Expressly to 6.0.0 (in WildFly preview). * Apache CXF to 4.0.8. * Commons-Beanutils to 1.11.0, which resolves CVE-2025-48734. * WildFly Channel Maven Plugin to 1.0.25. * WildFly HTTP Client to 2.1.1.Final. * Narayana LRA to 1.0.1.Final. * Arquillian BOM to 1.9.5.Final. * Arquillian Testcontainers to 1.0.0.Alpha4. * Caffeine to 3.2.1. * Apache Kafka to 3.9.1. * SmallRye OpenAPI to 4.0.11. * Nimbus Jose JWT to 10.3. * Artemis WildFly Integration to 2.0.4.Final. * MVC Krazo integration to 2.0.0.Final. * OWASP Dependency Check Plugin to 12.1.3. For a complete list of bug fixes, tasks, sub-tasks, and other changes, please refer to the . We encourage the community to test this beta release and provide feedback to help us stabilize WildFly 37.

26 Jun 2025 12:00am GMT