Application developers can use the Internet email infrastructure to move SOAP messages as either email text or attachments. The examples shown below offer one way to carry SOAP messages, and should not be construed as being the standard way of doing so. The SOAP Version 1.2 specifications do not specify such a binding. However, there is a non-normative W3C Note [SOAP Email Binding] describing an email binding for SOAP, its main purpose being to demonstrate the application of the general SOAP Protocol Binding Framework described in [SOAP Part 1].

This document describes a binding of SOAP [SOAP] into SMTP[SMTP]. Unlike previously published bindings, this binding ensures that the SOAP message is attached using Base64-encoding[BASE64] MIME[MIME] attachment. This greatly reduces the chance of mail scanners and SPAM filters modifying the SOAP body.

SOAP [1] is a lightweight protocol for exchange of information in a decentralized, distributed environment, using XML. This document details transporting SOAP messages over the Simple Mail Transport Protocol (SMTP). [2]

This document is meant to be an illustration of the SOAP 1.2 Protocol Binding Framework applied to a well known internet transport mechanism, Email, specifically rfc2822.

Ausgangspunkt für Wikieinträge über Dokumentation

Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value. (Article)

Nat Pryce presents the reengineering effort made to transform a legacy system through incremental improvement, the development process implemented, the results and some takeaway lessons learned.

David Nolen critiques the tools, languages and methodologies used today from the perspective of solving the “mapping dilemma”, introducing match, a pattern matching library for Clojure.