Re: [rest-dev] [External] : EE11 Platform call update

[Jan Supol <jan.supol@xxxxxxxxxx>]

Thank you for sharing, Jim.

+1 for Jakarta REST 4.0 in EE11, with @Context​ deprecated and kept as we planned for 3.2.

4.0 has a capability to overcome potential incompatibilities when moving towards CDI injection, while it can keep compatibility with 3.1 when using the 3.1 legacy injection. It would also allow a path for MP.next to move from @Context​.

Thanks,

Jan

---

From: rest-dev <rest-dev-bounces@xxxxxxxxxxx> on behalf of James Perkins via rest-dev <rest-dev@xxxxxxxxxxx>
Sent: Tuesday, February 20, 2024 10:49 PM
To: Jakarta Rest project developer discussions <rest-dev@xxxxxxxxxxx>
Cc: James Perkins <jperkins@xxxxxxxxxx>
Subject: Re: [rest-dev] [External] : EE11 Platform call update

 

On Tue, Feb 20, 2024 at 12:22 PM Santiago Pericasgeertsen via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

Jim,

 Thanks for the update.

 - On 3.2: I have not seen proof that we can do 3.2 with the suggested changes (deprecations) without breaking backward compatibility. I am skeptical.

My concern here is there will be no path forward for projects like MicroProfile if we simply just remove the @Context injection. If we drop @Context support, say in Jakarta EE 12, there is a very likely chance you can't have a Jakarta EE 12 deployment that works with some MicroProfile specifications and/or implementations. I know for sure there are several API's and implementations that use @Context injection for their REST endpoints.

 

 - On 3.1 for EE11: No objections.

 - On 4.0 for JAXB deprecation: Seems OK at first glance.

Just for a personal preference, I like the idea of what we have planned for 3.2, in a 4.0 which removes JAXB. That part is just my opinion though :)

 

— Santiago

On Feb 20, 2024, at 2:03 PM, Jim Krueger via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

Hi,

In this morning's EE11 Platform call there was renewed concerns about the possibility that Jakarta Rest may need to remain on 3.1 for EE11. The primary point of concern centered around the fact that XML binding would be moving to optional in EE11. This will cause a problem for Jakarta Rest since the deprecated dependency with JAXB is not slated for removal prior to JAkarta Rest 4.0. It was discussed that we might be asked to put out Jakarta Rest 4.0 containing only the removal of the JAXB dependency. I'd also assume if our work with release-3.2 reaches a point where it could be included in EE11 that there would likely be a push to rename 3.2 to 4.0 in order to allow the JAXB dependency removal to be included.

I was not in a position to advocate a course of action. I felt that the group should be made aware of this discussion.

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://accounts.eclipse.org__;!!ACWV5N9M2RV99hQ!OKE2-3coiWbO1poF9zfNNnIeHBWQ8QGhrpflT-cPEApEZxWsoYIlXpIg0Pz5ElVotc6exqiXp5S8q5WMQ2972MSCKRgw$

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

--

James R. Perkins

JBoss by Red Hat