Part 31 · Applications

Specialist Spring projects: choose the protocol

Prerequisites: 01-ecosystem

Which specialist fits the requirement?

External requirement: protocol or workflow; SOAP contract: Spring Web Services; Directory access: Spring LDAP; Resource links: Spring HATEOAS. Connections: External requirement to SOAP contract (XML schema); External requirement to Directory access (directory contract); External requirement to Resource links (hypermedia contract)
These are alternatives for distinct needs. REST Docs, Shell and Web Flow add other focused capabilities. [S01] [S60] [S61] [S62]

Goal & mental model verified

The portfolio includes specialist tools: Web Services for contract-first SOAP, LDAP for directory access, HATEOAS for links, REST Docs for tested documentation, Shell for CLIs and Web Flow for controlled navigation.

[S01] [S60]

Worked example · design exercise synthesis

Use SOAP integration for an insurer’s fixed XML contract; LDAP when identity data lives in a directory. Use REST Docs to connect documented API examples to tests rather than maintaining unrelated examples manually.

[S01] [S60] [S61] [S62]

Engineering decision synthesis

Match the external contract first, then select the adapter/framework. Specialized projects reduce plumbing but add protocol and lifecycle knowledge; they are not mandatory for every Boot application.

[S01] [S60] [S61] [S62]

Pitfall & diagnosis synthesis

An older tutorial may reference an Attic project as if it were a current default. Attic status requires checking migration/replacement guidance; it is not a blanket statement about every existing deployment.

[S01] [S60] [S61] [S62]

Improve & validate synthesis

Inventory specialty protocols and historical dependencies. Read each selected project’s current support and migration notes before adoption or replacement.

[S01] [S60] [S61] [S62]
Keep this: Use the smallest set of projects that honors your actual contracts.
Check yourself: Should a REST-only service add Spring Web Services?

Usually no. Its purpose is SOAP/XML-oriented service integration.

Sources & further reading

  1. [S01] Spring portfolio and Attic

    Spring project maintainers · documentation · accessed 2026-10-09 · Documentation retrieved 2026-10-09

    Supports: Portfolio roles; Current projects and historical Attic entries

    Read the linked section to validate the mechanism and its version-specific constraints.

  2. [S60] Spring Web Services

    Spring project maintainers · documentation · accessed 2026-10-09 · Documentation retrieved 2026-10-09

    Supports: Contract-first SOAP; XML schema and message endpoints

    Read the linked section to validate the mechanism and its version-specific constraints.

  3. [S61] Spring LDAP

    Spring project maintainers · documentation · accessed 2026-10-09 · Documentation retrieved 2026-10-09

    Supports: LDAP integration

    Read the linked section to validate the mechanism and its version-specific constraints.

  4. [S62] Spring HATEOAS

    Spring project maintainers · documentation · accessed 2026-10-09 · Documentation retrieved 2026-10-09

    Supports: Representation models; Links and affordances

    Read the linked section to validate the mechanism and its version-specific constraints.