| Re: [rest-dev] @Context removal vs. deprecation |
I think we all should be honest this time. In the past we made plans that apparently nobody could (or wanted to) put into practice. Do we really have the time to invest all needed resources to finally get rid of JAX-RS's historic non-CDI injection framework? Or will we end up with the same situation, that we all are +1 for doing so, but few weeks before deadline we all notice that time runs out and we didn't even start? Having that said, I am still +1 for getting rid of @Context, but we should only consent if we really all want to and are willing to invest into it (in particular all vendors, as this feature mostly will stress THEM). If we do not see that it will happen in time again, we maybe should simply give up that plan and concentrate on smaller things? -Markus Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jim Krueger via rest-dev 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 |