Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rest-dev] [External] : Jakarta Rest 3.2?
  • From: Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx>
  • Date: Fri, 12 Jan 2024 17:45:47 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=oeYJVde48uimyrObx8dodoOD2pGRXAuo4eAK85+Yp1Y=; b=espZdZAZwiybBFhOp/8b1WKcPNAjrx9bwdlPkf/TOI/mKNDWM8lWMTm0cxlqRJwCmkuDyKDvmfnnqwSrGyoMs/3+MxdYomghKFAKqEEpR0BnwtieJZsHnk5UK2GNlYAiZdP3CeUYDeg2xu9EZDifKUxCrC/phlsrnPcsbbW1WJIb40j4wTdyvW9NVQZhFJETiC/rpxr32XEQFpiA269Dg6cGYXxJJ2L1DCX5d4P9YYNHMxN9Jly4FEwklsJRr/eBUf51eMTvsDBJtjP6+9YvmtuoISV1+8XcRJGcV963feMe2pKg4d0kEewrX+JxHjSinnh3jK37H/D0Hvi0Rb1XAw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=Jad637+jI68y4YLH3OAr6BbSyrptE+6/q8dH9ZrquWYmcQocfdhX0GWXXsgZXZdvTTUD36iqCUS9F/JgHJ/REm9xEQQKdOVCoSNHifnUaxoCQLAXmtglwT4w6PE8F5EbwPjpvGR7vzZXxNZxNL7YIWD92TyMHYZnIwv41sThRFarbe7oSD7ZCg99UfmP2o3gUCF//FAZD3twkwyi9mwziG1aVDf+9MvShv2KlSIh+LhJatoEbeKz8rem54YzpvQ9D/wIYKAYm2TMO52gMnYTfHbVmyVnv0r+1P2tULU3o4Xjhts2P3GgcGiY4RXWPTgDOGZNr2yYTVjIAHE8wsgh+g==
  • Delivered-to: rest-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHaRV7m/+YPIyLMTkehxxcwn+yUYbDWc44A
  • Thread-topic: [External] : [rest-dev] Jakarta Rest 3.2?


 Thanks for attending those meetings and putting together this new proposal.


— Santiago

On Jan 12, 2024, at 8:54 AM, Jim Krueger via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

The purpose of this note is to gauge the interest within the Jakarta Rest community for a RESTful Web Services version 3.2.
The primary impetus for this proposed version would be to deliver a version where @Context injection is formally deprecated.   This would require an alternative implementation and all of the corresponding API and TCK changes/additions, but would not remove backward compatibility for current users.    The current plan for Jakarta Rest 4.0 introduces a breaking change by removing @Context injection .   While 4.0 should still focus on that and I’m aware that both the 3.1 specification and Javadoc for the Context class indicate that it will be removed in a “future release”, I’m wondering if it wouldn’t be a good idea to formally deprecate this first, allowing users to see the deprecation warnings and prepare.
In addition, at this point it would seem that the likelihood of Jakarta Rest-4.0’s inclusion in Jakarta EE11 is tenuous at best, so producing a more limited 3.2 Version, that still has value add, might be more of a realistic goal along with easing the eventual transition to tighter integration with CDI.
rest-dev mailing list
To unsubscribe from this list, visit;!!ACWV5N9M2RV99hQ!IFs8OxUIubzlMCUIQSfkc6W_fAFhoRU3a8dPAdwIIj1FkFabY6wnhODrsteeUoxO49eVK7UQcalRN_jP409DrYtGEBTW$

Back to the top