plz help me this assignment Which of the following changes is NOT backwards comp
ID: 3704319 • Letter: P
Question
plz help me this assignment
Which of the following changes is NOT backwards compatible ? (Chapter 10)
Adding a new standard method to an existing REST resource
Adding new binding and service definitions to a WSDL
Adding a new WSDL portType definition and associated operations
Adding additional conditions before accepting legacy generator content
Software that has designed to support later extensions is said to be ______________________ (Chapter 10)
A) stateless
backwards compatible
forwards compatible
D) synchronous
Which HTTP header lets you specify whether a RESTful service is to return XML or JSON ? (Chapter 9)
Expect
User-Agent
Accept
Authorization
The ___________ soap:body attribute within a WSDL binding construct states that XML Schema data types are used (Chapter 8)
style="RPC"
use="literal"
use="encoded"
style="document"
A)Adding a new standard method to an existing REST resource
B)Adding new binding and service definitions to a WSDL
C)Adding a new WSDL portType definition and associated operations
D)Adding additional conditions before accepting legacy generator content
Explanation / Answer
Q. Which of the following changes is NOT backwards compatible ?
Answer :B. Adding new binding and service definitions to a WSDL
Explanation :
WSDL actually acts as a contract more than an interface. The WSDL describes exactly what the operation expects to "receive" and what it expects to "return". The closest analogy to this would be in C changing the prototype for a function without changing the function itself, they wont match and that causes problems.
The more specific the WSDL is the more behavior you are "guaranteeing" to be in place.
If you need flexibility in your returned data (i.e. adding/removing fields etc) you can do one of the following:
Version your WSDL definitions and publish services that can redirect older versions to newer versions
Use more abstract data return types, such as XML to hide the complexity or changing data.
has some more risk, but it can be managed with XSDs or other technologies. Your particular project requirements will dictate what is acceptable.
Q. Software that has designed to support later extensions is said to be
Answer : A) stateless
Q.Which HTTP header lets you specify whether a RESTful service is to return XML or JSON ?
Answer : C. Accept
At server side, an incoming request may have an entity attached to it. To determine it’s type, server uses the HTTP request header Content-Type. Some common examples of content types are “text/plain”, “application/xml”, “text/html”, “application/json”, “image/gif”, and “image/jpeg”.
Content-Type: application/json
Similarly, to determine what type of representation is desired at client side, HTTP header ACCEPT is used. It will have one of the values as mentioned for Content-Type above.
Accept: application/json
Generally, if no Accept header is present in the request, the server can send pre-configured default representation type.
Q. The ___________ soap:body attribute within a WSDL binding construct states that XML Schema data types are used
Answer :B)use="literal"
Explanation :
The soap:binding element indicates that this is a SOAP 1.1 binding. It also indicates the default style of service (possible values include document or rpc) along with the required transport protocol (HTTP in this case). The soap:operation element defines the SOAPAction HTTP header value for each operation. And the soap:body element defines how the message parts appear inside of the SOAP Body element (possible values include literal or encoded). There are other binding-specific details that can be specified this way.
Using document style in SOAP indicates that the body will contain an XML document, and that the message parts specify the XML elements that will be placed there. Using rpc style in SOAP indicates that the body will contain an XML representation of a method call and that the message parts represent the parameters to the method.
The use attribute specifies the encoding that should be used to translate the abstract message parts into a concrete representation. In the case of 'encoded', the abstract definitions are translated into a concrete format by applying the SOAP encoding rules. In the case of 'literal', the abstract type definitions become the concrete definitions themselves (they're 'literal' definitions). In this case, you can simply inspect the XML Schema type
Thanks...
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.