Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rest-dev] Jakarta REST work for EE 11
  • From: Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx>
  • Date: Mon, 26 Jun 2023 15:40:10 +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=tXsGfdFhZZA5/ffFVdGKZU7GzUvOcxh2tNbI8G/7Fy0=; b=obOP/v12FEYB66fbmXt6W4jHnQM7ihxyEb274dLCzdXqVE4FZffVsvdn3cOW3WDJuE5UppkrfkZOdJIIOHSd9b/vGPcoOca+bE2ZfSxDmGBojsQdWhuV7PC9LZSdus6Ln14mWgEHpK9nX5/2VT41U47BTBIgLDpPfnzG20MQBIRGq6w4G7Y9D4od0pl2Up8p2KZCrlSJn2GICtw7P5bY/yKnNVEzdLYs1xBEqSHNZpcm/HEtG7xWufIR43KukHA1SCbGnhXd2fqYzWU0XfGAyhtcHEnNX7FcbfMrd1LW308B/d9jeh8NvuaapTt9gomU5U3jK0SdqKauEi3YwgyUzg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=e+DMGEOtZUkB79TZBIHqnx3je8/chaYe6FQ8L468s/kAedaXHnrg6l2v1RNAaOn6/i2DsJd95EC9D3XRSO23ZyCiE5LOCWSS68PiRXAIgCT8v/RdvrsImoktNexZDE0JXYMSnw2CErKxtz1VF5wrp/gT1+vMfcsGTFyDYWg7qMGamlvr1EmaFJ7TKrOVnryOO5HRJmnq0iraTJ+sWFHdR6QmSj+uYsd3Pus/7MvX7YJ4uL6XdqQBqIFwa7vANickSW1SUN0vjKGFGDcQkmrsFw28GEKezveKca86QaOh71AY8w+HQBdkirtbUunIr2oHSmUU8JeGuXtlkQ8KrAuczg==
  • Delivered-to: rest-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHZjLGi3QwxIVuZ90OuVh27y5a74K+db4sA
  • Thread-topic: Jakarta REST work for EE 11

On May 22, 2023, at 9:30 AM, Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx> wrote:

Dear Jakarta REST experts,

As all of you know, Jakarta EE 11 planning is now underway. We are being asked to create a PR on the specifications repo and get the work started on the new API. Our current plan, which seems to align very nicely with the EE platform goals, is to make changes to the REST API and specification to better integrate with CDI, as a way to simplify our "injection strategy" and also to better integrate with other specifications.

Unfortunately, it is unlikely I will be able to commit substantially to this effort before the last couple of months of the year. The purpose of this communication is to __ask for help__ during this period in order to start the work ASAP. I should be able to review parts of the work submitted in the next few months, but will not have the time to create it myself.

The initial step should be to create at least one GitHub epic from which we can create individual issues for people to investigate. I volunteer to create such an epic and thus help kickstart the new API and spec work.

 Epic has been created:

 Feel free to extend, link issues, creates issues from Epic, etc. See also branch 'release-4.0'. 

 Hopefully this epic can get us going with the 4.0 work.

 Thanks for those that already volunteered.

— Santiago

Back to the top