Service composition
Building one solution out of parts other projects published: a reuse package brings its models, code, initial data and texts into your project through npm or Maven, you serve what you reference and extend what you import, and the same modules deploy as one application or as several on a shared database. Distinct from service integrationService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from destinations, which is how the address and the credentials are found, and from replication, which is holding the data locally.SAP and community, narrow by design, which reaches a service that stays deployed elsewhere, and from tenant extensibilityTenant extensibilityLetting a customer extend the model of a running SaaS application with extra fields and entities per tenant, without forking the application, as distinct from extending the application's code for every customer at once.SAP and community, unassessed, which is a subscriber extending a running SaaS.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Resolves a reuse package from a Maven dependency: the CDS, CSV and i18n files under a cds folder in the JAR's resources are extracted by the CDS Maven plugin and embedded in the project like an npm package.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Artifacts
Details
Coverage
For your agent
- Ref
capability:service-composition- JSON
- /capabilities/service-composition.json
- MCP
- Connecting an agent