Plugin authoring
Writing a package that extends the CAP runtime rather than an application that uses it — the mechanism underneath every cds-plugin in this atlas, and the question you arrive at once solving a problem twice makes you want to solve it once for everyone.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Extension points for CAP Java plugins: CDS models shared as Maven artifacts and resolved into the project, and event handlers registered for custom types and annotations.
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
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2AlwaysA plugin is developed or distributed for use with SAP CAP materials covered by the agreement.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
The agreement expressly includes plug-ins among the SAP materials and section 2 addresses making APIs and tools available to third parties. A plugin's own open-source licence does not erase those separate use terms.
SAP Developer License Agreement 3.2 CAP →Artifacts
Details
Coverage
For your agent
- Ref
capability:plugin-authoring- JSON
- /capabilities/plugin-authoring.json
- MCP
- Connecting an agent