SCDJWS 2. Soap
•Transferir como ODP, PDF•
1 gostou•1,222 visualizações
It's cover the SOAP's part about the SCDJWS certification. Refers to: 1. SCDJWS 5.0 Study Guide by Mikalai Zaikin 2. SCDJWS 5 Study Notes by Ivan A Krizsan
![[object Object],[object Object]](https://image.slidesharecdn.com/2-soap-110817104326-phpapp01/85/SCDJWS-2-Soap-1-320.jpg)
![[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Mais procurados
Semelhante a SCDJWS 2. Soap
Semelhante a SCDJWS 2. Soap (20)
Mais de Francesco Ierna
Mais de Francesco Ierna (14)
Último
Último (20)
SCDJWS 2. Soap
- 10. Specifies how a SOAP reiceiver processes a SOAP message.
- 12. Processed by a URL
- 14. Processed by a URI known as the SOAP role name
- 15. Invariant during the proccessing of an individual SOAP message
- 20. First child of the enveloppe.
- 25. Should namespaces qualified
- 26. May contain XML well-formed or be empty
- 27. Contains or data or fault
- 29. Must not contain a Document Type Declaration
- 30. Must not contain Processing Instructions
- 31. Should not contain the namespace declaration xmlns:xml=" http://www.w3.org/XML/1998/namespace "
- 32. Must not contain soap:encodingStyle attributes on any elements belonging to the same namespace as the SOAP <Envelope> element
- 33. Any soap:mustUnderstand attribute appearing in a SOAP Envelope is only allowed to have t he value “0” or “1”.
- 34. SOAP elements must not have attributes belonging to the same namespace asthe SOAP <Envelope> element ( http://schemas.xmlsoap.org/soap/envelope/ ): <Envelope>, <Header>, <Body>
- 36. A receiver of a SOAP message that contains a mandatory header block targeted at the receiver, using the soap:role attribute in the header block, must generate a “soap:MustUnderstand” fault if the receiver does not understand the header block
- 37. When a fault is generated, the receiver should not perform any further processing of the SOAP Envelope, except for any processing required to roll back the effects of the processing of the SOAP Envelope up to the point of the fault.
- 38. If the normal processing of a SOAP Envelope would have resulted in a SOAP response being sent, a receiver must transmit a fault in place of the response if a fault is generated.
- 40. The above child elements of a SOAP <Fault> element must not be namespace qualified .
- 41. A receiver of a fault must be able to handle faults in which the <faultstring> element has a xml:lang attribute.
- 44. A HTTP request message must be sent using the HTTP POST method.
- 45. SOAPAction HTTP header field in a HTTP request message must be a quoted string.
- 47. 405 Method not Allowed” should be used when the method of a HTTP request message is not POST.
- 51. Extensibility can be used to add capabilities found in richer messaging enveroiment
- 54. Possible reasons for faults may be improper message formatting, version mismatches, trouble processing a header and application-specific errors
- 55. A SOAP fault is generated by the node, be it an intermediary or the ultimate receiver
- 56. If the messaging exchange pattern One-Way is used, then the SOAP fault must not be transmitted to the immediate sender. The SOAP fault may be stored somewhere
- 76. Handlers are invoked with a message context , which provides methods that the handler uses to access and modify inbound or outbound messages.
- 79. handleFault() is called when a message contains a protocol fault.
- 80. close() is called after the completion of message processing by all handlers for each web service invocation,