Either Loosely or Tightly Coupled
Neither Loosely nor Tightly Coupled
Both Loosely and Tightly Coupled
The overall structure of the XML message
The conventions representing the remote procedure call in the XML message
A binding to HTTP
The type of client to be used
The conventions to wrap and send an error back to the sender
True, because it allows functional specification like schemas and WSDL to be stored in it.
False, because the actual content is never stored in UDDI.
True, because it allows implementation details to be stored in it.
False, because the actual content is always stored in UDDI.
True, because it also allows business documents like schemas and WSDL to be stored in it.
Asynchronous Query Pattern
Command Facade Pattern
Message Bus Pattern
None of the above
SOAPAction HTTP header is optional in SOAP 1.2.
SOAP 1.2 permits partially transmitted and sparse arrays.
SOAPAction HTTP header is mandatory in SOAP 1.2.
SOAP 1.2 disallows partially transmitted and sparse arrays.
SOAP 1.2 adds a new standard header for reporting additional information in "MustUnderstand" faults.
'.asmx' is the ASP.NET file extension for XML Web Services.
With ASP.NET you have to write your own WSDL and SOAP documents.
Use "WebMethod" to mark the functions in your application that you would like to make into web services.
The namespace "System.Web.Services" is from the .NET framework.
Document/literal Wrapped style of WSDL originates from JAX-RPC provided by SUN Microsystems.
JAXB 1.0 provided validation at marshal time.
JAXB 2.0 allows validation at unmarshal and marshal time.
JAXB 2.0 enabled on-demand validation on a JAXB content tree.
JAXB 1.0 provided validation at unmarshal time.
JAXB 1.0 enabled on-demand validation on a JAXB content tree.
Direct Invocation Interface
Dynamic Invocation Interface
With JAX-WS, the developer generates/parses SOAP messages.
The JAX-WS runtime system converts the API calls and responses to and from SOAP messages.
A JAX-WS client cannot access a web service that is not running on the Java platform, and vice versa.
The starting point for developing a JAX-WS web service is a Java class annotated with the javax.jws.WebService annotation.
For a JAX-WS Endpoint: The implementing class should not explicitly reference an SEI through the endpointInterface element of the @WebService annotation.
The <types> element defines the data type that are used by the web service.
The <binding> element defines the message format and protocol details for each port.
The <types> element defines the data elements of an operation.
The <binding> element defines only the protocol details for each port.
The <message> element defines the data elements of an operation.
TCP/IP or UDP port on the server
The operations that can be performed, and the messages that are involved
The actual protocol used in the Web Service
Only the operations that can be performed
Only the messages that are involved including their types and elements to be used
Configuration Driven Service
Here's an interesting quiz for you.