Migrate, Modernize and Build Java Web Apps on Azure: This live workshop will cover methods to enhance Java application development workflow.
Modern Digital Website Security: Prepare to face any form of malicious web activity and enable your sites to optimally serve your customers.
Principal Technical Trainer at readlearncode.com @alextheedom
About
Alex Theedom is an instructor, Java champion, Java developer/architect with years of experience developing Java EE and Spring applications in a variety of sectors including finance, gambling and e-learning. I provide Java EE training on LinkedIn learning and I am the author of "Java EE 8: Only what’s new" a straight-to-the-point book covering only what’s new in Java EE 8.
Stats
Reputation: | 1601 |
Pageviews: | 1.1M |
Articles: | 26 |
Comments: | 7 |
Articles
Comments
Sep 18, 2018 · Jordan Baker
Think about Richardson Maturity Model in terms of pizzas https://dzone.com/articles/richardson-maturity-model-and-pizzas
Mar 01, 2018 · Michael_Gates
Java EE has always been standards driven and so will Jakarta EE. The standards that were overseen by the JCP will now be maintained and advanced by Eclipse EE.next Working Group. So Jakarta EE will be the new Enterprise Java standard. The change is a great opportunity to address some of the shortcomings of the old way. I personally hope to see shorter release cycles and greater community engagement leading to a more nimble, relevant Enterprise Java but still backed by standards. And the reason for choosing Jakarta EE will still be the same as for choosing Java EE and I hope a few more reason will be added by the coming changes. I see Jakarta EE and Spring as different animals of the same species. They satisfy different management requirements as you have alluded to in your question. Java EE gave reassurance through standards and blue-chip stewardship and Spring gives innovation and spunkiness.
Alex.
Sep 01, 2017 · Michael_Gates
Use POST when creating a new resource and PUT when making a complete (not partial) update. Use PATCH for a partial update. However, JAX-RS does not implement PATCH so you should consider using POST to an identifiable URI (contains the resource ID). PUT can be used for creating resources in the circumstances mentioned by Matt Crowe above. In the end, as long as it's documented well you can do what solves your problem best.
Aug 31, 2017 · Michael_Gates
Hi Prasanth,
In a simple example, we used POST to create and PUT to update. Check this link: http://www.restapitutorial.com/lessons/httpmethods.html however, in reality, it is not as clear cut. Take a look at Oracle's JAX-RS docs: https://docs.oracle.com/javaee/7/tutorial/jaxrs002.htm#GIPYS. So you can use POST and PUT to create but there are semantic differences. Whatever you decided to do the most important is to ensure it is crystal clear what the RESTful API contract is and it is well documented.
Thanks for the question. This is a good one for further discussion. How does everyone else reading this use POST/PUT?
Aug 21, 2017 · James Sugrue
Hey Abhishek. Nice post about @Context. There are many uses for the @Context. Such as injecting Request, Application, Configuration, ResourceContext, ServletConfig, ServletContext, HttpServletRequest/Response & UriInfo as detailed in this article What is javax.ws.rs.core.context?
Aug 18, 2017 · Arran Glen
Hi Sebastien. Thanks for the comment. Its great to see examples of how other people handle the same situation. I have updated the original article and mentioned your real-word solution: https://readlearncode.com/java-ee/java-ee-jax-rs-bean-validation-failure-management/
Dec 22, 2015 · John Vester
Thanks for your comment Thai. You will find much more examples and deeper discussions in my book Professional Java EE Design Patterns.