(Sending again, somehow formatting was lost)
Jakarta RESTFul Web Services 5.0
- Deprecate @Context and context resolvers in preparation for CDI adoption
- Evaluate alternative using CDI as part of this release
- Consider introduction of new @Entity annotation
- Deprecate @Suspended
- Remove Security Manager uses in API
- Evaluate integration with Jakarta HTTP specification
- Consider support for default @Param annotations
- Clarify provider injection support in Jakarta REST Client API
- Review Servlet integration in preparation for CDI adoption
- Add support for Java records
Hi All,
As you know, the deadline is approaching to submit a plan for EE 12. I went over some of our e-mail discussions and collected what I considered to be the most important items for the plan. I need to create a few more issues, so none are linked in the
plan yet.
I’m hoping to submit this plan on Monday 14th.
— Santiago
----
Jakarta RESTFul Web Services 5.0
-
Deprecate @Context and context resolvers in preparation for CDI adoption - Evaluate alternative using CDI as part of this release - Consider introduction of new @Entity annotation - Deprecate @Suspended - Remove Security Manager uses in API - Evaluate integration
with Jakarta HTTP specification - Consider support for default @Param annotations - Clarify provider injection support in Jakarta REST Client API - Review Servlet integration in preparation for CDI adoption - Add support for Java records
----
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://urldefense.com/v3/__https://accounts.eclipse.org__;!!ACWV5N9M2RV99hQ!PXbDZk4xKXilTAfJHFi3zwSapshbT19qmTcvPHswZo96aWGrMWHUByhotkV-AaBOOogdZRYwTZsSwCqvKrvnVLxmrGCw$
_______________________________________________