Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BETA BLOG - Jakarta Restful Web Services 4.0 (EE11) #28707

Open
jim-krueger opened this issue Jun 10, 2024 · 0 comments
Open

BETA BLOG - Jakarta Restful Web Services 4.0 (EE11) #28707

jim-krueger opened this issue Jun 10, 2024 · 0 comments
Assignees
Labels
Blog jakartaEE11 target:beta The Epic or Issue is targetted for the next beta target:24007-beta

Comments

@jim-krueger
Copy link
Member

jim-krueger commented Jun 10, 2024

The information you provide here will be included in the Open Liberty beta blog post (example), which will be published on openliberty.io/blog/, and potentially elsewhere, to promote this beta feature/function of Open Liberty. For this post to be included in the beta issue please make sure that this is completed by the end of Friday following the GM (Tuesday). The beta and release blogs are created using automation and rely on you following the template's structure. DO NOT REMOVE/ALTER THE <GHA> TAGS THROUGHOUT THIS TEMPLATE.

<GHA-BLOG-SUMMARY>

Please provide a summary of the update, including the following points:

  • A sentence or two that introduces the update to someone new to the general technology/concept.

Jakarta RESTful Web Services provides a foundational API to develop web services following the Representational State Transfer (REST) architectural pattern.

  • The Human-readable name and short feature name for your feature- eg WebSockets feature (websockets-1.0).

restfulWS-4.0, restfulWSClient-4.0

  • Who is the target persona? Who do you expect to use the update? eg application developer, operations.

These features are for application developers.

  • What was the problem before and how does your update make their life better? (Why should they care?)

This release represents in incremental improvements made to Jakarta RESTful Web Services provided in 4.0 release of that Jakarta project. It provides new convenience API methods, such as the containsHeaderString() method in ContainerRequestContext, ContainerResponseContext, and HttpHeaders to determine if a Header contains a specified value, a new UriInfo.getMatchedResourceTemplate() method that returns a full template for a request, and also the addition of MediaType values APPLICATION_JSON_PATCH_JSON and APPLICATION_MERGE_PATCH_JSON.

  • Briefly explain how to make your update work. Include screenshots, diagrams, and/or code snippets, and provide a server.xml snippet.
   <featureManager>
        <feature>restfulWS-4.0</feature>
    </featureManager>

or

<featureManager>
     <feature>restfulWSClient-4.0</feature>
 </featureManager>
  • Where can they find out more about this specific update (eg Open Liberty docs, Javadoc) and/or the wider technology?

More information can be found at the https://jakarta.ee/specifications/restful-ws/4.0/ website including the javadoc.

</GHA-BLOG-SUMMARY>

What happens next?

  • Add the label to the blog issue for the beta you're targeting (e.g. target:YY00X-beta).
  • Make sure this blog post is linked back to the Epic for this feature/function.
  • Your paragraph will be included in the beta blog post. It might be edited for style and consistency.
  • You will be asked to review a draft before publication.
    • Once you've approved the code review, close this issue.
  • If you would also like to write a standalone blog post about your update (highly recommended), raise an issue on the Open Liberty blogs repo. State in the issue that the blog post relates to a specific release so that we can ensure it is published on an appropriate date (it won't be the same day as the beta blog post).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blog jakartaEE11 target:beta The Epic or Issue is targetted for the next beta target:24007-beta
Projects
None yet
Development

No branches or pull requests

1 participant