Products / Technology
Web Services Technology
How the Web Services Edition maps a model to a service contract, and which parts of the stack the generated project relies on.
Technology notes
From model to contract
A service contract describes operations, messages and the data types that travel between them. In the Web Services Edition, each of those parts has a counterpart in the model. Generation maps the model to the contract and writes the code that implements it.
- Operations in the model become contract operations.
- Model types become the data types in the contract.
- Service references become the client wiring for consumers.
- Deployment settings select the target server and transport.
Stack at a glance
| Contract | Service description for operations and types |
|---|---|
| Messages | SOAP and XML payloads for the generated operations |
| Transport | HTTP, configured per deployment |
| Runtime | Spring context inside a servlet or application server |
Contract discipline. Publish the contract before the implementation. Consumers can then build against a stable description while the implementation is generated and refined.
Read the Web Services Edition overview for the development paths, and the packaging recipe for deployment settings.