A2A Jakarta 1.1.0.Final is released!
I am pleased to announce the 1.1.0.Final release of A2A Jakarta, the Jakarta integration for the A2A Java SDK.
This release upgrades A2A Jakarta to a2a-java 1.4.0.Final. Most of the work in this release comes from that upgrade, together with the corresponding integration changes in A2A Jakarta.
Aligned with a2a-java 1.4.0.Final
a2a-java 1.4.0.Final includes a range of improvements to the server and client SDKs. These include more robust streaming behaviour, improved handling of task push-notification configuration, fixes for multi-tenancy and agent-card resolution, and REST support for the application/a2a+json media type. There are also fixes for gRPC interoperability and task handling.
For a fuller account of the upstream changes, see the a2a-java 1.4.0.Final release announcement and the release notes.
Enterprise deployment example
We have also verified that A2A Jakarta can use the distributed, enterprise-oriented components provided by a2a-java. The enterprise example runs an A2A agent across two WildFly nodes, using JPA-backed task and push-notification stores together with a Kafka-backed replicated queue manager. This allows task state and live events to be shared in a load-balanced deployment.
The original A2A Java SDK cloud-native enhancements article explains the purpose of these components and the considerations for running an A2A agent in a distributed environment.
For more information, see the project repository and its README. If you have any issues with the project, please open an issue. Pull requests are welcome!
