REST stands for Representational State Transfer and is a newer addition to the web service family.

Roy Fielding coined the acronym REST in his Ph.D dissertation to describe an architectural style in the design of scalable web services.

1. What are the differences between SOAP web services and REST web services?

2. If REST can support multiple MIME types such as XML, Text, JSON, user-defined etc. then how do server and client know about what the other is sending?

3. What are the different ways in which you can secure a REST web service?

4. What are microservices? 

Web fragments are xml files that will have part of the configurations of a web.xml. There can be many web fragments, and when the application is deployed container will combine all the fragments and will treat it like a single web.xml. Similar to annotations, now developers can write web fragments for their modules and application assemblers would not have to add them to the web.xml file. We can override annotation behavior with a web fragment or web.xml.

Annotations were introduced to reduce the burden of Application assemblers who would otherwise have to combine every developer’s configuration details into the web.xml file. Thus annotations allow for pluggability of the code by allowing developers to specify configurations on their own classes and hence application assemblers would not have to add them to the web.xml file. We can still use web.xml to override any of the configuration given by an annotation.

Methods related to getPart will throw IOException if an I/O error occurred during the retrieval of the Part components of this request, ServletException if this request is not of type multipart/form-data or IllegalStateException if the request body is larger than maxRequestSize, or any Part in the request is larger than maxFileSize.