A2A Java SDK for Jakarta 0.3.0.Beta1 is released!

The change list can be found here.

We have done a lot of reorganisation of both projects so they are more modular.

Also, following some upgrades to our internal infrastructure, we are now able to deploy the artifacts to Maven Central under the org.wildfly.a2a groupId.

Aside from that the major new features are the inclusion of the transports introduced in version 0.3.0 of the A2A Protocol specification: * [gRPC] - This relies on the WildFly gRPC Feature Pack. * [HTTP+JSON] - Also referred to as REST.

We pass the TCK for both these new transports, as well as the original JSON-RPC transport.

A simple example showing how to package an agent for use with both transports can be found here.

Rather than going into a full example here, the starting point is to include one or both of the following dependencies in your application: * org.wildfly.a2a:a2a-java-sdk-jakarta-jsonrpc:0.3.0.Beta1 - to enable the JSON-RPC protocol * org.wildfly.a2a:a2a-java-sdk-jakarta-grpc:0.3.0.Beta1 - to enable the gRPC protocol. * org.wildfly.a2a:a2a-java-sdk-jakarta-rest:0.3.0.Beta1 - to enable the HTTP+JSON protocol.

The simple example provides more guidance for how to manage the dependencies. Additionally, you need to provide CDI beans which provide the AgentCard and AgentExecutor implementations for your Agent as per the A2A specification.

Note that the simple example is more of a "Hello world" type application focused on how to package your application for use with the A2A Java SDK for Jakarta.

Once you have packaged your application, see the examples in the A2A Java SDK repository, and the Java samples in the a2a-samples repository for how to actually implement agents that communicate with each other.

You can then, for example, try to replace one of those agents with one running on WildFly. To help with integrating LLMs in WildFly applications, we have the WildFly AI Feature Pack which leverages Langchain4j to interact with the LLM.

For more background information about the A2A Java SDK, and the A2A Java SDK for Jakarta, see our previous blog posts. Note that the blog posts are written using various versions of the SDK, so you will likely need to make some adjustments.

We would like to investigate if we can provide the dependencies in a nicer way so all the exclusions seen in the current version of the sample are no longer required.

Additionally, we will continue improving the implementations in both repositories, and of course keep up as the A2A Protocol specification evolves.