Re: [agentic-ai-dev] Jakarta EE Roadmap Narrative: your input needed by

[Reza Rahman <reza_rahman@xxxxxxxx>]

Honestly, up to you how you want to update the narrative. I don’t really have the full context there. I just want to make sure we are clearly communicating what we are actually aligned on in the project currently. Also up to you if you want to wait to see what folks think, though what I proposed is probably the closest to current known project consensus.

In the meantime, is there anything else useful I can share? For example, it terms of project status, the M1 is published and we are aiming to get the 1.0 release process started in the next month or so. This will ultimately require a specification committee vote, so there are no guarantees. One level down, the spec and API is pretty much ready to go already. The TCK still has some gaps that we need to work through. I think the supporting implementation is in decent shape. In parallel we are working on the website, tutorial, and examples, but those are really not part of the official specification.

On Oct 12, 2026, at 12:05 PM, Dominika Tasarz-Sochacka <dominika.tasarz@xxxxxxxx> wrote:



Thank you, Reza - the roadmap wording is only a draft, so it's useful to get your feedback at this stage. 

Steve and I are comfortable with the approach you describe: standalone by default, then evaluating inclusion after each release and asking the platform project.

One option for the changes in the narrative we want to make public would be to show Agentic AI as a standalone spec on its own cadence, with platform inclusion as something to be evaluated rather than planned. We can also keep the EE 12 data foundations (NoSQL, Jakarta Data) separate from the Agentic AI tiles, so nothing suggests it ships with EE 12. This is only a suggestion and I'm happy to consider other ideas?

Many thanks,

Dominika Tasarz-Sochacka
Senior Developer Advocate (Payara, Jakarta EE & Foojay) at Azul

From: Reza Rahman <reza_rahman@xxxxxxxx>
Date: Monday, 12 October 2026 at 16:23
To: agentic-ai developer discussions <agentic-ai-dev@xxxxxxxxxxx>
Cc: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>; Steve Butler <steve.butler@xxxxxxxx>; Tanja Obradovic <tanja.obradovic@xxxxxxxxxxxxxxxxxxxxxx>; Shabnam Mayel <shabnam.mayel@xxxxxxxxxxxxxxxxxxxxxx>; Dominika Tasarz-Sochacka <dominika.tasarz@xxxxxxxx>
Subject: Re: Jakarta EE Roadmap Narrative: your input needed by Fri 16 Oct

Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Folks,

I am starting this thread as this is not an insignificant decision, and I want to make sure we are all aligned before I respond to the request.

The suggestion here in the thread below is to include the spec as a pretty prominent part of the EE 13 platform (for perspective, that’s probably about 3 years out). This might be tentatively/directionally OK, but I do think in practicality the proposed positioning needs to be altered significantly. Let me explain my thinking but I really need folks in the project to seriously weigh in.

As you well know, we are currently a standalone specification with no short term plans to seek inclusion into the platform. We have been clear about this from the start and this was one of the key factors considered during the specification ballot.

You all understand the reasons behind this. We are forging new ground in a very rapidly evolving space. While I am pretty sure our ideas are well grounded and in line with what is going on in the space, the work is very clearly experimental. We might be exactly right or we may need to significantly evolve the specification in the next few years based on what we learn as we move forward. Being a standalone specification allows us the freedom to experiment and grow our community in directions that makes sense for us. It may mean introducing significant breaking changes to meet the needs of the space or it may not. Furthermore, we are clearly a long way away from broad vendor support. No other specification I know of in EE has been included into the platform under such conditions.

In my view, the right time to begin thinking about being included in the platform would be when we are sure the API is pretty stable, we have real production users delivered through at least one high quality implementation, and we have clear industry traction. That might happen in the next 2-3 years and it might not. I personally have a hard time predicting that far out in the future.

So here is what I am proposing. We should plan to stay standalone by default and continue to have releases working through the backlog we already have and whatever we discover in the future. After each release, we can evaluate where we are. If we feel the conditions are right to pursue inclusion into the platform, we reach out to the platform project and gauge their opinion. If they give us a favorable indication, we will seriously propose inclusion. Otherwise, we table the conversation until the next release.

Can you please share your thoughts on this in the next few days? As you can see, I need to respond by Friday.

Thanks,

Reza

On Oct 9, 2026, at 6:25 AM, Dominika Tasarz-Sochacka <dominika.tasarz@xxxxxxxx> wrote:



Hi all,

Thank you for your input on the High-Level Jakarta Roadmap so far. The visual has been agreed with Ivar - the next step is expanding each tile into a short narrative we can use on the website, in talks and in customer conversations.

A first draft doc is here:

https://docs.google.com/document/d/1I66U7A6hZoa_oLzZGWBu9bTeA04JHhJ1/edit 

Could you review and add to the sections you know best by end of next week (Friday 16 October)? Each tile has a suggested reviewer, and anything marked [NEEDS INPUT] is where I need your technical details please.

Who I'm hoping will look at what:

* Otavio: AI Integration (NoSQL and vector data foundations) and Ecosystem Growth

* Reza: the Agentic AI tiles across 2026 to 2028, especially the EE 13 platform inclusion wording

* Kenji: Cloud Native, in particular the supply chain trust and EU CRA tile

* Ivar: a full review, plus Java alignment (EE 12 on Java 25, Java 29 on the horizon) and Developer Experience

* Steve: Developer Experience, especially tooling

Please edit directly or leave comments, whichever is easier. Even a quick "looks right" on your sections is helpful and if something is wrong or missing, just feel free to add and change.

The roadmap will be presented at the open call on the 20th of October, then if/when agreed, handed over for publication on the Jakarta EE website.

Many thanks,

Dominika Tasarz-Sochacka
Senior Developer Advocate (Payara, Jakarta EE & Foojay) at Azul