tailieunhanh - Programming Web Services with SOAPn phần 2

và "đốt hương" (từ "xu" như trong "xu"). Cùng với nhau, những rễ này có nghĩa là "nói dối về các đơn vị nhỏ của đồng tiền." Nhầm lẫn mang lại cố gắng tìm ra những gì có nghĩa là điều này sẽ giúp những kẻ xấu lúng túng và bị chiếm đóng lâu dài, đủ để họ không ăn cắp ứng dụng của bạn. | Programming Web Services with SOAP if it does not understand how to deal with the transaction header block the entire message must be rejected. This guarantees that the recipient understands transactions. Encoding Styles As part of the overall specification Section 5 of the SOAP standard introduces a concept known as encoding styles. An encoding style is a set of rules that define exactly how native application and platform data types are to be encoded into a common XML syntax. These are obviously for use with RPC-style SOAP. The encoding style for a particular set of XML elements is defined through the use of the encodingstyle attribute which can be placed anywhere in the document and applies to all subordinate children of the element on which it is located. For example the encodingstyle attribute on the getQuote element in the body of Example 2-5 indicates that all children of the getQuote element conform to the encoding style rules defined in Section 5. Example 2-5. The encodingstyle attribute s Envelope xmlns s http 2001 06 soap-envelope s Body n getQuote xmlns n urn QuoteService s encodingStyle http 2001 06 soap-encoding symbol xsi type xsd string IBM symbol n getQuote s Body s Envelope Even though the SOAP specification defines an encoding style in Section 5 it has been explicitly declared that no single style is the default serialization scheme. Why is this important Encoding styles are how applications on different platforms share information even though they may not have common data types or representations. The approach that the SOAP Section 5 encoding style takes is just one possible mechanism for providing this but it is not suitable in every situation. For example in the case where a SOAP message is used to exchange a purchase order that already has a defined XML syntax there is no need for the Section 5 encoding rules to be applied. The purchase order would simply be dropped into the Body section of the SOAP envelope as is.