Re: [rest-dev] [External] : @Context removal vs. deprecation

[Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx>]

 There’s a sentence in the spec about @Context deprecation. However, it wasn’t done the right way, which is by providing an alternative, mainly because as we are finding out that isn’t as straightforward as it seems.

— Santiago

On Mar 7, 2024, at 12:59 PM, Markus Karg via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

+1 for deprecating it. IMHO I thought that we already deprecated it. ;-)

-Markus

 

 

Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jim Krueger via rest-dev
Gesendet: Donnerstag, 7. März 2024 18:09
An: Jakarta Rest project developer discussions
Cc: Jim Krueger
Betreff: Re: [rest-dev] [External] : @Context removal vs. deprecation

 

Regardless of whether it is called 4.1 or 5.0.  It sounds like the consensus thus far is that @Context injection should be deprecated prior to being removed.   Are there any objections or concerns about this from others?

On Mar 7, 2024, at 10:42 AM, James Perkins via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

 

FWIW I'm okay with either the deprecation happening in 4.1 or a 5.0. That said, I do understand the desire to deprecate in 5.0 and remove in 6.0. It could help implementations handle the breaking changes a bit better so they themselves could break some compatibility.

 

On Thu, Mar 7, 2024 at 8:38 AM Jan Supol via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

Personally I prefer deprecation in a 5.0 (EE12) release prior to removal in a 6.0 release. That would help us with the possible compatibility issues related to the discussed CDI beans and Application methods. 

 

--Jan

---

From: rest-dev <rest-dev-bounces@xxxxxxxxxxx> on behalf of Jim Krueger via rest-dev <rest-dev@xxxxxxxxxxx>
Sent: Wednesday, March 6, 2024 7:53 PM
To: Jakarta Rest project developer discussions <rest-dev@xxxxxxxxxxx>
Cc: Jim Krueger <jckofbyron@xxxxxxxxx>
Subject: [External] : [rest-dev] @Context removal vs. deprecation

 

Hi, 

The proposed Jakarta RESTful Web Services 4.0 content (https://deploy-preview-705--jakartaee-specifications.netlify.app/specifications/restful-ws/4.0/) is currently under a “progress review” but is expected to pass within a week.

 

Assuming there are no problems, we can consider the 4.0 content to be set.   And, at least for now, that work will continue in the “main” branch.

 

That brings us to the discussion of what will be next.   Do we push for a version 5.0 that removes @Context injection entirely or a 4.1 version that deprecates @Context injection and provides an alternative implementation?    Both of these options carry many/most of the same concerns and some good progress has been made in the “release-3.2” branch toward deprecation..  

 

So the question is, should this deprecation work continue in a “release-4.1” working branch  or be abandon in favor of a “release-5.0” that removes @Context injection.

 

Personally I prefer deprecation in a 4.1 release prior to removal in a 5.0 release, unless a blocking issue is discovered.  What is your opinion?

 

Thanks

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

 

-- 

James R. Perkins

JBoss by Red Hat

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

 

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