Specialist Spring projects: choose the protocol
Prerequisites: 01-ecosystem
Which specialist fits the requirement?
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]Check yourself: Should a REST-only service add Spring Web Services?
Usually no. Its purpose is SOAP/XML-oriented service integration.